None of my workflows are triggering. The AI said to have the owner restart the instance, which I did and it didn’t help. I can’t get anyone in support to actually support their product. No cap has been reached. Manual trigger works.
Manual trigger working while nothing else fires is usually one of three things, and none of them throw an error.
First, on recent n8n versions the active toggle alone is not enough, the workflow has to be published too (that is the change the docs link above covers). Open one of the dead workflows and check its publish state, not just the active switch.
Second, if it is published, open the executions list and filter to queued and running. If executions pile up there, the workflow is fine and the runner is the problem: on self hosted with queue mode that means the workers went down, on cloud it is usually something pausing execution on the plan side.
Third, webhook triggers after a restart are sneaky: the outside service (Telegram, Shopify, whatever) still posts to the webhook URL it registered at activation. If the instance came back on a different URL, deactivate and reactivate the workflow so it re-registers, then fire one real event.
What is your setup, cloud or self hosted, and which trigger do the dead workflows use? That narrows it fast.
Did the last successful automatic runs all stop at the same time, even for workflows with different triggers? That timestamp would give Cloud support a specific window to check.
For any workflow that creates or updates records, can you see which
items came in after that last run? If so, you’ll have a list to
compare with what actually got processed once the triggers are back.
That should help you decide which items need replaying.
Nothing has come in since the last runs except when I run them manually, so not sure what to compare. I can tell what came in when I ran them manually.
I meant the app that normally sends items to n8n. For example, if a
form starts the workflow, does the form itself show any submissions
after the last automatic run? If it does, you can compare those with
the ones your manual runs picked up. If the source has no history, the
execution list alone can’t tell you what was missed. Thanks for
clarifying, Shannon.
This is Jon from the support team. Please can you let me know your support ticket ID or send me the instance name in a private message and I will take a look.
Good luck with the update tomorrow. If they still don’t fire after it, the 8:00 timestamp is the useful bit for support. Cloud stopping everything at once like that doesn’t look like a workflow problem to me