GENERIC_TIMEZONE value for UTC GMT?

Questions
1

Have the UTC or GMT values been added as accepted GENERIC_TIMEZONE options (as mentioned in Default Timezone Issues)

When I set either of these as a variable, I still don’t see this option in the Workflow pulldown and the pulldown reports Default - Default Timezone not valid

`
n8n:
image: docker.n8n.io/n8nio/n8n
restart: unless-stopped
ports:
- “5678:5678”
environment:
- N8N_PORT=5678
- N8N_PROTOCOL=http
- TZ=UTC
- GENERIC_TIMEZONE=UTC
- N8N_RUNNERS_ENABLED=true
- N8N_SECURE_COOKIE=false
volumes:
- n8n_data:/home/node/.n8n

`

Information on n8n setup

  • n8n version: 1.81.4
  • Running n8n via Docker
  • Operating system: Ubuntu 22.04.5 LTS
1 Like
2

I’m not sure I understand your question, but to set your timezone you can use these environment variables:

  • GENERIC_TIMEZONE
  • TZ

You can then verify the current time by using the $now function in any field and observe the output.

:point_right: If my reply answers your question please remember to mark it as the solution

3

Is “UTC” a valid option?

If not, what is the correct option if I want to use UTC throughout n8n?

If UTC is a valid option, why do my workflows say this?

image
image1021×481 28.9 KB

1 Like
4

You are correct, you do not understand the question.

He’s referring to the ability to set UTC, which has not worked for a long time.

5

As of version 1.81.0 (which is the version I am currently on), no, you still cannot use UTC, and the error you are seeing is the same I see, when attempted the same way you are attempting.

6

So is there no “neutral” (no TZ) option within n8n?

7

I don’t think there can be a “no TZ” option. Every workflow inherently needs a TZ. It just defaults to Eastern US, for some reason I do not understand myself (popularity? appeal?).

8

I tried like you and got the same “not valid” so I just went with my current timezone.

UTC would be great as the default, I think they do not support it for a reason idk,

looking for answers as well :eyes:

9

there was a solution proposed in the link at the beginning of this thread, but it must be low priority.

10

I’m new to the n8N community. Is there a Jira-like site where backlogged feature requests can be voted upon?

11

We are adding those timezone options back in this PR.

2 Likes
12

This is great, I think this should be the default as well!
Thanks

13

New version [email protected] got released which includes the GitHub PR 13999.

2 Likes
14

perfect :pray:t2::tada:

15

Thank you. Once I figured out that tag 1.85.4 != latest, things fell right into place.

    environment:
...
      - TZ=Etc/UTC
      - GENERIC_TIMEZONE=Etc/UTC

image
image1282×280 19.7 KB

1 Like
16

The Etc/UTC option is now visible/valid within the workflow, but my execution logs still display in local time. New n8n user here. Am I missing another setting?

image
image1204×666 88.3 KB

Debug info

core

  • n8nVersion: 1.85.4
  • platform: docker (self-hosted)
  • nodeJsVersion: 20.18.3
  • database: sqlite
  • executionMode: regular
  • concurrency: -1

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: memory
17

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.