Updated: 28 September 2026 · Applies to: n8n 2.40 (Docker Compose)

If a scheduled n8n workflow starts at the wrong hour, the timezone is not set. Out of the box a self-hosted n8n uses America/New_York. Nodes that work with time, such as the Schedule Trigger, use that timezone to decide when to run.

Set the timezone (Docker Compose)

  1. Find your timezone name in the list of timezones, for example Asia/Kolkata, Asia/Dubai, Europe/London or America/Chicago.
  2. Open your .env file (or the environment: section of compose.yaml) and set both values:
    GENERIC_TIMEZONE=Asia/Kolkata
    TZ=Asia/Kolkata
    GENERIC_TIMEZONE sets the timezone of schedule-oriented nodes; TZ sets the system timezone of the container, which controls what scripts and commands such as date return. In the Compose file of How to install n8n with Docker Compose and HTTPS on an Ubuntu VPS? both are taken from GENERIC_TIMEZONE in .env.
  3. Apply the change:
    cd ~/n8n-compose
    sudo docker compose up -d
  4. Check the time inside the container:
    sudo docker compose exec n8n date

Set the timezone with docker run

Add -e GENERIC_TIMEZONE="Asia/Kolkata" -e TZ="Asia/Kolkata" to your docker run command and start the container again with the same volume.

Different timezone for one workflow

Open the workflow, then its Settings, and choose a Timezone there. This overrides the instance setting for that workflow only.

Check that schedules run correctly

  • A Schedule Trigger set to 09:00 runs at 09:00 in the timezone that applies to the workflow, not at 09:00 of your computer.
  • After changing the timezone, open the workflow and check the trigger's time: the workflow keeps its cron settings and is now evaluated in the new timezone.
  • The times shown in Executions follow the same setting. Compare one execution with a clock.

Frequently asked questions

Do I need to restart n8n after changing the timezone?
Yes. Environment variables are read when the container starts; docker compose up -d recreates the container with the new values.

Does the server's own timezone matter?
Not for n8n in Docker: the container has its own TZ setting. The server's clock should still be correct; check it with timedatectl.

Official documentation: n8n documentation: Set the timezone.

Need a server for n8n, or a hand with the setup?

Prefer a hand with the setup? Our engineers can do it for you: Hire an Expert, or use our on-demand server management.

Was this answer helpful?

Still stuck? Open a ticket