Since November 5th, 2026, at approximately 3:02 p.m. (CET) or 2:02 p.m. UTC, my instance yina-ai.app.n8n.cloud has not been executing any production runs (webhooks, scheduled triggers). According to my usage dashboard, my account quota has not been exceeded: [Plan: __, Usage: __ of __ executions, Billing period __].
What we’ve observed:
The last successful production execution ran at 2:02:41 p.m. UTC (execution 7429, with sub-executions 7483 through 7485).
A workflow with a scheduled trigger (ID f3UzHPXB4KpRVb3B, every 5 minutes) last ran at 1:59:01 p.m. UTC (execution 7479). The expected runs at 2:04 and 2:09 p.m. UTC did not occur.
Production webhook calls (workflow oWScepLNyoLmMLms) return {"code":0,"message":"There was a problem executing the workflow"}, and no execution is created.
Starting the same workflow in production mode via the n8n interface at 2:07 and 2:09 p.m. UTC returned: “Execution limit reached. Consider upgrading your plan” (link with source=executions_error_max_executions).
Manual executions continue to work normally (for example, execution 7486 at 2:07:06 p.m. UTC).
The instance is reporting that the execution limit has been reached, even though my account shows available quota. Please investigate why the instance is reporting this (unsynchronized counter or another limit) and restore production executions. This is urgent: Videos are scheduled for automatic publication tomorrow, November 6th, at 10:00 a.m.
Note: These findings come from an analysis by Claude, Anthropic’s AI assistant, which is connected to my instance via the n8n MCP interface. Claude identified the problem through the missing scheduled executions, the webhook error, and the “Execution limit reached” response when starting in production mode.
Hi @TT934, “Execution limit reached” is the message n8n Cloud uses for the monthly execution quota. The concurrency limit normally queues extra runs. The monthly quota normally leaves a Failed entry under Overview → Executions, so the missing webhook and schedule entries are worth flagging.
In your support request, include a screenshot of Cloud Console → Overview showing your plan and used/allowed execution count. Ask support to compare it with the quota the workspace enforced at 14:07 and 14:09 UTC on November 5. Include execution 7429 as the last successful production run.
Quota-blocked runs won’t replay automatically. Before rescheduling the missed videos, check which ones already went live.
First verify the dashboard’s billing-period boundary and time zone, then compare them with the production-run timestamps; manual and production executions may be counted differently. Since production returns an explicit limit error while manual runs succeed, add that response, UTC timestamps, and one successful manual-run ID to the existing support ticket and request a workspace counter or entitlement check. Keep scheduled retries paused until the limit is confirmed clear, then test one production trigger to avoid a backlog burst.
Your execution count had hit the limit for this month, which is why production runs were blocked while manual runs still worked. The usual automated reset didn’t go through, so I reset it manually as a one-time reset. The count is back to 0 and the instance is running.
I’ve replied to your support ticket with the same update, and I’m posting here for visibility for anyone else who hits this.
Executions blocked while the limit was active were not run afterwards, so please check anything that was scheduled between 5 Nov 14:02 UTC and now.
The workflow on a 5 minute schedule uses a lot of executions over a month. Because this was a one-time reset, a plan upgrade is the way to get more executions if you hit the limit again.
If you have any further issues, please reply to me on the support ticket.