Strange problem with timezone calculations - only affecting scheduled runs

[joeldeteves]

Describe the issue/error/question

I’m having a strange problem with timezone calculations on one of my scheduled executions - each time it runs, it is supposed to calculate the current date minus 1 hour and compare it to a timestamp retrieved from an RSS feed.

However, whenever it calculates the current date, it seems to return the wrong date (for example today is November 1st, but it is returning October 31st).

That said, if I run the execution manually, it returns the correct date of Nov 1st so I am unsure where the problem is (it only seems to affect the job when it executes automatically).

What is the error message (if any)?

Example of an automated run:

Example of a manual run:

Please share the workflow

Share the output returned by the last node

Information on your n8n setup

• n8n version: 0.200.1
• Database you’re using (default: SQLite): Postgres
• Running n8n with the execution process [own(default), main]: own
• Running n8n via [Docker, npm, n8n.cloud, desktop app]: k8s

[joeldeteves]

I think I misunderstood the problem completely and it threw me off.

It turns out the timestamp in the RSS feed is in UTC, whereas my default Timezone in n8n is set to PST.

So in the end the problem wasn’t the automation at all - it had to do with that I should have been setting my 1hourAgo calculation to subtract from the UTC date instead: