We’re on n8n Cloud (Business tier).
Code nodes fail with:
“Your Code node task was not matched to a runner within the timeout period.”
This happens even on the first Code node.
Failed execution link:
Earlier nodes execute normally.
We’re the only active execution.
This appears to be a task runner provisioning/health issue.
What is the error message (if any)?
Task request timed out after 60 seconds
Your Code node task was not matched to a runner within the timeout period. This indicates that the task runner is currently down, or not ready, or at capacity, so it cannot service your task.
If you are repeatedly executing Code nodes with long-running tasks across your instance, please space them apart to give the runner time to catch up. If this does not describe your use case, please open a GitHub issue or reach out to support.
Have you already spaced code node task apart to give the runner time to catch up? If so, please open a GitHub issue or reach out to support.
An emergency workaround I’ve seen some teams use is to move simple logic to Set nodes, IF/Switch nodes, or expressions, and temporarily avoid Code nodes until the runner stabilizes.
PS: I don’t recommend restructuring complex workflows just for this. The issue is not structural to your workflow.
The sample workflow that I attached is really just a manual execution node and a simple code node with return true. Not even this can run. Unfortunately, I have more complex logic that a set node won’t support.
I don’t know how to contact support other than via this forum.
I got access to the owner account and restarted the instance. This resolved the issue. It seems like we should be able to delegate that function so it’s not blocked behind a single user.