N8n Cloud (Community Edition) — some daily scheduled workflows show "Error" or "No Execution" this morning (24 March) — manual run works fine

Questions
, ,
1

This morning (24 March 2026), several of my daily workflows — all scheduled to run at 9:00 AM Europe/Berlin — showed unexpected results in the execution log. Some showed “Error”, others showed no execution at all. Not all workflows were affected.

When I click into the errored executions, there is no node highlighted and no error detail — just “Error” at the top level, which suggests the problem is at the trigger/scheduler level, not within any node.

Manually running all affected workflows works perfectly every time.

Setup:

  • Platform: n8n Cloud (Community Edition)

  • Trigger: Schedule Trigger — daily at 9:00 AM

  • Timezone: Default — Europe/Berlin (set on all workflows)

  • n8n status page: All systems operational

My suspicion: Given that Europe/Berlin switches to CEST (UTC+2) this coming Sunday, 29 March, I wonder if there’s a DST-related scheduler edge case being triggered a few days early. This has never happened before and I haven’t changed anything.

Has anyone else seen this today? Any ideas what might cause a trigger-level error with no node detail?

2

Hi @maraalbasio-create , welcome to the n8n community!

I wouldn’t put my money on DST here, because Europe/Berlin only switches on March 29, so seeing this on March 24 would feel odd to me; since the manual runs work and the failed ones show either a top-level error with no node highlighted or no execution at all, my first guess would be a scheduler-side hiccup on the Cloud side rather than something wrong in your workflows themselves. I’d probably post the exact timestamp, mention that several workflows with the same 9:00 Europe/Berlin schedule were affected while others were not, and ask whether anyone else on n8n Cloud saw missed or trigger-level schedule failures this morning, because that would help tell whether this was a one-off workspace issue or a broader scheduler problem.

3

Thank you! I’ll do just that then. :slight_smile:

1 Like
4

Great, let me know if it worked.

5

Unfortunately I realized we’re on the community plan, so I don’t think contacting n8n Cloud support is an option for me. :frowning: I’ll monitor these workflows closely and let you know if I it was more than just a one-off hiccup! Thanks again.