error fix
N8N Timezone Wrong
Wrong times in n8n usually come from mismatched instance timezone variables, workflow timezone settings, server/container time, or schedule trigger expectations.
Independent third-party notes. n8n is a trademark of its owner and is referenced only for compatibility and troubleshooting context.
Quick Answer
Wrong times in n8n usually come from mismatched instance timezone variables, workflow timezone settings, server/container time, or schedule trigger expectations.
Key Facts
- Docker variables
- n8n Docker setups commonly set TZ and GENERIC_TIMEZONE.
- Workflow setting
- Individual workflow settings include a timezone option.
- Schedule impact
- Schedule-oriented nodes depend on timezone interpretation.
- Debug split
- Distinguish display timezone, workflow timezone, and server/container timezone.
Recommended Steps
- Check the instance-level timezone variables in the deployment.
- Check the workflow timezone in workflow settings.
- Confirm the server or container time is correct.
- Test a Schedule Trigger with a near-future time.
- Document the intended timezone for the deployment and workflows.
Verification
- A near-future scheduled workflow fires at the expected local time.
- Displayed execution timestamps match the expected timezone context.
- The deployment variables and workflow settings no longer conflict.
Warnings
- Changing timezone settings can affect existing schedules.
- Do not assume the browser timezone, container timezone, and workflow timezone are the same.
Common Mistakes
- Setting TZ but forgetting GENERIC_TIMEZONE.
- Changing instance timezone while leaving workflow timezone different.
- Testing with daylight saving time dates without checking the intended timezone database name.
Examples
TZ=Asia/Shanghai
GENERIC_TIMEZONE=Asia/Shanghai
Workflow settings timezone=Asia/Shanghai
Server/container time checked=yesFAQ
Why did my schedule trigger one hour off?
Timezone mismatch or daylight saving rules are common causes. Check workflow timezone and instance-level timezone settings together.
Should all workflows use the same timezone?
Usually yes for a single business or region. If not, document each workflow's expected timezone.