Unverified50% confidenceSolutionExact time
The original text suggests writing every crontab hour in the scheduler's own time zone, using comments to explain what the local time means on either side of the clock change, and configuring a deploy freeze window for each scheduled run.
1
Sources
50%
Confidence
Long-term
Relevance
10/17/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe Schedule node runs workflows automatically on a time basis, supporting triggers at a fixed time each day, every hour, or at custom intervals.74% similarVerifiedA robust scheduling system should store all timestamps in UTC and perform localized conversion at the presentation layer based on the user's current context.73% similarUnverifiedGENERIC_TIMEZONE determines the default timezone used at the workflow level (including Schedule Trigger, logs, and time functions in expressions).73% similarUnverifiedThe Cron expression of a Schedule Trigger itself carries no timezone information, and its interpretation depends on the default timezone of the execution environment.73% similarUnverifiedFor deadlines involving UTC timezones, separate local-time calendar reminders should be set with a buffer of at least 24 hours.72% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1052311API
curl https://kongchang.com/api/v1/knowledge/claims/1052311MCP
get_claim(id=1052311)