Review brief timestamps across timezones: source, task and carrier clocks

Identify the event before comparing timezone, units and ordering

Current Radar parses date_str using fixed yyyy-MM-dd HH:mm in UTC+08:00. Last successful source read cannot be replaced with a phone request, cache hit or file modification. Optional task timestamp is a separate Unix-time field; Watch sourceDate and capturedAt also differ. Establish event/contract first instead of treating all times as equivalent numbers.

Different from cache diagnosis and batch comparison

Cache review locates old data/read failures; batch review establishes comparable exports. Here different time meanings can be compared incorrectly. No automatic timezone converter, clock repair, scheduling or cross-zone sync is added, and no live source time is rewritten.

Time meanings and units

Time/location Current meaning/contract Check Does not replace
date_str Last successful source read, fixed UTC+08 format Exact string, source and successful read state Refresh tap or exported-file save time
Task timestamp Optional Double, Unix task-update time Producer units, absence/null and ordering scope Whole-source read, approval or handling time
Phone request Local event starting a read New successful source response versus cache Source update or task modification
Watch sourceDate Source represented by the phone summary Scope, failures and truncation Watch packaging or independent refresh
Watch capturedAt Summary packaging time Inspect separately from sourceDate New business state or successful source read
File/editorial time Save/copy/edit event Whether only a copy/document changed Original business event or source identity
Unix seconds/milliseconds Different units, not interchangeable Producer/consumer contract Automatic conversion based on digit count
Other-zone presentation Another display of one instant Explicit offset, date boundary and applicable rules Writing local-zone text back as date_str

Watch dates use that carrier’s Date encoding contract. Do not subtract arbitrary serialized values directly from task Unix fields without verifying format/units. This page supplies no universal timestamp detector.

Two fixed historical illustrations

A: 2026-10-18 09:00 under date_str's UTC+08 contract
Same instant in UTC: 2026-10-18 01:00 UTC

B: 2026-10-18 00:30 at UTC+08
Same instant in UTC: 2026-10-17 16:30 UTC, on the preceding date

These are explicit-offset illustrations, not real/current source data. A UTC display does not authorize appending Z, offsets or ISO separators to date_str. Its strict round-trip format is not arbitrary ISO8601 acceptance.

Review sequence

Label the event first: source read, task update, request, packaging or editing. Confirm identity/scope, then format, timezone/offset and unit. If ordering conflicts, inspect absent timestamps, priorities and source-order rules before assuming clock failure or changed task state.

Current source marks source age over 24 hours stale and flags time more than five minutes ahead. These are freshness signals, not response latency, refresh frequency, service SLA or a business deadline. Keep unknown/failed times rather than filling now to hide a warning. Corrections belong to the original maintenance process without bypassing parsing/write authority.

FAQ

Does another phone timezone change date_str parsing?

The current model fixes UTC+08 rather than inferring from device location. Keep displayed time and source meaning separate.

Is adding Z or +08:00 automatically more compatible?

No. The consumer has an exact format/round-trip check. A source-format change needs actual-version compatibility review.

Can a 13-digit value automatically be divided by 1000?

Do not repair by digit count. Confirm producer contract/field first. Wrong units can be invalid or mean another instant; no automatic coercion is offered.

Why is source time old after refresh or packaging?

Request/packaging events differ from successful source reads. Cache can retain an old source time; do not substitute now.

Are 24 hours and five minutes refresh SLAs?

No. They are current stale/future-source thresholds, not promised update schedules or task-handling deadlines.

Can missing time be filled with now to help comparison?

That fabricates meaning. Keep the gap and confirm at the source instead of presenting old data/edited copies as new facts.

Reading and source

JSON types/nulls · Batch comparison · Cross-device presentation · Format compatibility · Start · Privacy

Evidence: source-date parsing/freshness/sorting, Watch date model.