Think² logoThink²
Sign in

Guides (Spanish)

Before scheduling a reminder: does that local time occur once, twice or not at all?

‘At 1:30 in New York’ does not always identify a single instant. During a clock change it may occur twice; another time may not exist. Adding an IANA zone lets you consult its rules, but you must still resolve ambiguity with the person requesting the reminder. This guide provides six synthetic cases and local code: it created no reminders, tested no calendars and does not demonstrate that Think² automatically resolves these cases.

Waitlist: no guarantee of immediate access or a free plan. The destination is in Spanish.

Situations to review

The same 01:30 occurs twice.

For 2026-11-01 01:30 in America/New_York, the test using tzdata2026c retains two candidates: 05:30 UTC with offset −04:00 and 06:30 UTC with offset −05:00. Both fold=0 and fold=1 return to the same wall time.

Do not choose the first for convenience. Ask for the instant to be confirmed, showing both options with date and offset. The zone is present, but the request is still ambiguous.

The requested 02:30 did not exist that day.

For 2026-03-08 02:30 in America/New_York, neither attempt returns to 02:30: one returns to 03:30 and the other to 01:30. Constructing a datetime with ZoneInfo did not itself reject the input; our round-trip check found that neither candidate was valid.

Do not silently turn the request into 03:30. Ask for a valid time and preserve the agreed correction. Detecting a nonexistent time does not authorise moving the reminder.

09:00 is unique, but its UTC equivalent changes with the date.

America/New_York at 09:00 yielded 13:00 UTC on 15 July 2026 and 14:00 UTC on 16 November. America/Bogota at 09:00 on 16 November yielded 14:00 UTC. An input of 09:00 without a zone was classified falta_zona: the computer’s zone was not used to fill it in.

Do not replace a rule-based zone with a fixed offset copied from another day. A one-time match with Bogotá does not make the zones equivalent. If the zone is missing, ask which one applies.

Waitlist: no guarantee of immediate access or a free plan. The destination is in Spanish.

How to evaluate the work

  1. Wall time means the date and time as written by the person, before a unique instant has been identified. An IANA zone such as America/New_York provides historical rules and offset changes; UTC identifies the instant once the choice has been resolved. This test does not interpret phrases such as ‘tomorrow’, ambiguous abbreviations or the sender’s time zone.
  2. We fixed six synthetic inputs and expected candidates before execution. For the five inputs with zones, the script tries fold=0 and fold=1, converts each to UTC and back to the zone. It keeps only candidates whose local date and wall time exactly match the input, then deduplicates equal UTC values. Zero candidates is classified inexistente (nonexistent), one unico (unique), and two ambiguo (ambiguous). Without a zone it does not attempt conversion. This is our own educational method for these cases, not a general validator tested across the entire IANA database.
  3. Original results with Python 3.13.5 and system IANA data tzdata2026c: case | local date and time | zone | classification | UTC candidates Z1 | 2026-11-16 09:00 | America/Bogota | unique | 14:00 Z2 | 2026-11-01 01:30 | America/New_York | ambiguous | 05:30 and 06:30 Z3 | 2026-03-08 02:30 | America/New_York | nonexistent | none Z4 | 2026-07-15 09:00 | America/New_York | unique | 13:00 Z5 | 2026-11-16 09:00 | America/New_York | unique | 14:00 Z6 | 2026-11-16 09:00 | no zone | falta_zona (missing zone) | not calculated All listed UTC values fall on the same date as their row’s local date. Six matches with our prior expectations are not six independent validations.
  4. Python’s documentation explains fold for ambiguous times: 0 uses the offset before the transition and 1 the offset after it. At an ordinary time, both attempts may yield the same UTC, so they are deduplicated. Do not interpret fold=1 as ‘add an hour’ for any zone or permission to select the second occurrence.
  5. Before configuring an action, keep the requested local date and wall time, IANA identifier, candidates found and confirmed decision. For a one-off reminder, make the selected instant explicit with its offset or UTC, then display it again in the requested zone. This is our own design recommendation, not a format imposed by Python or a calendar guarantee.
  6. A recurring reminder ‘at 09:00 local time’ is not equivalent to repeating the same UTC time. This test calculated only six individual dates: it did not test recurrences or policies for future changes. Inspect the actual service’s rules and recheck according to its policy and current time-zone data; do not decide to skip or move an occurrence without agreement.
  7. The download contains the protocol, script and original results, including both attempts per input. It requires Python 3.9+ with zoneinfo and installed IANA data, from the system or the tzdata package. Python documents that when neither source is found, ZoneInfo may raise ZoneInfoNotFoundError. Missing data is not a ‘nonexistent time’ result. The script does not turn that failure or an invalid identifier into an assumed zone.
  8. The delivered package itself was extracted into separate new data and code directories and executed once with Python -I, absolute paths and a working directory outside the data. It exited with code 0 and all six rows matched the originals. The separate check preserves the date, command, environment and new output. This is a reproduction on the same machine, not a second factual source or a calendar test. Other versions of time-zone data may change results; permanent agreement is not promised.
  9. No accounts were connected, reminders configured, messages sent or calendar or Think² policies tested. A unique instant does not demonstrate that an action will execute on time, that a notification will be delivered or that someone will receive it. Keep the time decision separate from evidence of an actual execution.

Download the evidence

Frequently asked questions

Is attaching ZoneInfo enough to reject a nonexistent time?

Not in this test. Both 02:30 datetime values were constructed; only conversion to UTC and back showed they did not preserve 02:30. The guide does not attribute automatic validation to ZoneInfo that it did not perform.

What if someone asks for ‘at nine’ with no zone?

Ask for an explicit date and zone before configuring the action. The script preserves falta_zona and does not adopt the computer’s settings. It also does not interpret natural language or a person’s location.

Does this prove a reminder will arrive correctly?

No. It resolves an earlier ambiguity using synthetic data; it does not measure delivery or punctuality. A calendar or assistant may apply different rules and needs its own check. The Think² waitlist does not guarantee immediate access.

Sources and scope

  • Python — zoneinfo — IANA data sources, fold and missing-data errors; no calendar or Think² test.

Waitlist: no guarantee of immediate access or a free plan. The destination is in Spanish.