Active workflow not executing

Questions
1

I have a workflow that delivers the expected results when i trigger it manually. I’ve activated the “active” toggle but i still don’t see it executing on schedule (every __ hours).

The workflow shows active.
I’ve updated to the latest stable version.

Thoughts?

1 Like
2

Assuming you are using the scheduled trigger node, first please check the execution log for production executions (this is disabled by default so you have to enable it to see production executions) so that you can see where your workflow might be failing or executing successfully but not giving the desired outcome.

3

Hi @meplumb

This is a classic issue with self-hosted n8n. The problem is almost always the timezone .
Your server is running in a different time (likely UTC) than the browser where you set the schedule.
The Fix: You need to set the timezone environment variable for your n8n instance.
Add this environment variable to your setup (e.g., your docker-compose.yml file):

  • GENERIC_TIMEZONE=Your/Timezone

  • (Example: America/New_York, Europe/Berlin)
    You must restart n8n after adding this variable.

This should immediately fix your scheduling problem. If it still doesn’t work, check your Executions log to see if the workflow is trying to run but failing instantly.

If you found this helpful, please mark it as the solution and give it a like .

1 Like
4

Thank you for your reply. I double-checked that and see “Save failed production executions“ “Save successful production executions“ and “Save manual executions“ all set to “Default - Save”
”Save execution progress” was set to “Default - Do not save” and i switched that for now to see if there’s an impact.
Thank you again.

5

Thank you. I have played around with self-hosted n8n, but this workflow is in the cloud.
I’m still going through to check for any potential timezone impacts/settings.

Thank you.

6

None of the situations applied and none of the recommended actions resolved the issue.

I deleted the trigger, put it in anew, and it works.

1 Like
7

I have the same problem as you. I have been detecting it in the last 3 weeks let’s say.

A few workflows that are active are not triggering when they have to. They did, and you can check it in the executions, but for a reason that I don’t know, they stopped triggering.

In my docker compose file, since the beggining of the installation of n8n, I had GENERIC_TIMEZONE=Asia/Tokyo which is the one that correspond to the place where I live.

So I tend to think that this is not a problem of the “timezone”, but something that has to do with changes in the last versions.

It has occured to some workflows. I have tried copying and pasting in a new workflow. It works but, if I make a manual trigger, then the schedule triggers stops working.

I have tried changing the frequency of the trigger and it doesn’t work.

It is a little bit painful, because know I can not trust in any scheduled trigger. May be they will trigger, may be they will not.