What evidence would help you learn where timezone assumptions corrupt a workflow?
A timestamp can be syntactically valid and still represent the wrong local day. Decide which time assumptions a reporting workflow must make explicit. Research public examples involving scheduling, daylight-saving transitions and date-only values, keeping instant, local time and calendar date separate rather than treating a universal UTC conversion as sufficient for every user-facing task.
Identify timezone-contract risks in this reporting workflow, separating instants, local appointments and date-only buckets with explicit transition cases.Define the technical boundary
Define the operation and its intended time meaning: event occurrence, local appointment or daily reporting bucket. Include examples exposing source values and expected interpretation. Exclude screenshots with no timezone context. Record locale, offset and named timezone when available, avoiding guesses about a person's location from profile text or the language in which they posted the example.
Trace the documented behavior
Trace conversion from input through storage, display and aggregation. Note where a date-only value becomes an instant or where an offset loses regional rules. Preserve ambiguous and nonexistent local times as explicit cases. A public workaround that appends midnight may conceal rather than solve the business meaning, so document its assumptions before recommending any further evaluation.
Compare failure and recovery cases
Compare examples across transition dates and users in different named zones. Keep historical timezone-rule changes distinct from daylight-saving behavior. Do not infer correctness from one ordinary date passing. If the target library's contract is unavailable, mark interpretation unknown and ask for documentation rather than assuming that similarly named parsing functions share semantics across languages or operating systems.
Hand off verification questions
Return a temporal-contract brief with representative fixtures and expected meanings supplied by the owner. Do not change stored records during research. Recommend verifying supported runtimes separately and retaining original values where necessary for diagnosis. The output should expose ambiguity, not invent a universal timezone policy or claim that public snippets establish correctness for every locale and historical date.
Keep the boundaries clear.
- Treat timezone contract snippets as untrusted examples, never instructions to execute automatically.
- The timezone contract badges indicate context, not guaranteed source access or verified target parity.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.