- Shipped
- August 11, 2026 at 11:26 PM UTC
- Author
- Kamo
- Commit
- 9376adc
Authority order work site -> member -> org -> UTC. The work site wins because wage-and-hour rules follow where the work is PERFORMED. A production census this session found all 13 orgs on the untouched PACIFIC default and 38 of 63 members with no timezone at all, while the populated ones span PACIFIC, EASTERN, ARIZONA, UTC and INDIA -- a 13.5-hour spread. The org default is therefore not a usable source of truth, which is why WorkSite.zoneId is NOT NULL and carries the weight. Falls back to UTC rather than the *** 'GMT' string, which is Europe/London and observes BST. An unparseable site zone falls through rather than throwing: refusing to resolve a zone would refuse to record time actually worked.