Urgent: Task Runner Timeout After Account Reactivation - Account Not Provisioned

Questions
1

Dear n8n Support Team,

My n8n Cloud account was recently suspended due to payment issues. I have now paid my subscription and my account shows as active, but I’m experiencing critical errors across all my workflows.

Issue: All Code nodes are timing out with “Task request timed out after 60 seconds” errors. This appears to be a backend provisioning issue where task runners are not being matched to my account after reactivation.

Account Details:

  • n8n Cloud URL: tapancsahu3.app.n8n.cloud
  • n8n Version: 1.121.2 (Cloud)
  • Account Status: Active (Recently reactivated after payment)

What I’ve Tried:

  • Cleared browser cache
  • Logged out and back in
  • Re-saved and reactivated workflows
  • Issue persists across all workflows with Code nodes

Error Details:

{
  "errorMessage": "Task request timed out after 60 seconds",
  "errorDescription": "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.",
  "errorDetails": {},
  "n8nDetails": {
    "n8nVersion": "1.121.2 (Cloud)",
    "binaryDataMode": "filesystem",
    "stackTrace": [
      "Error: Task request timed out after 60 seconds",
      "    at LocalTaskRequester.requestExpired (/usr/local/lib/node_modules/n8n/src/task-runners/task-managers/task-requester.ts:291:17)",
      "    at LocalTaskRequester.onMessage (/usr/local/lib/node_modules/n8n/src/task-runners/task-managers/task-requester.ts:259:10)",
      "    at TaskBroker.handleRequestTimeout (/usr/local/lib/node_modules/n8n/src/task-runners/task-broker/task-broker.service.ts:115:50)",
      "    at Timeout.<anonymous> (/usr/local/lib/node_modules/n8n/src/task-runners/task-broker/task-broker.service.ts:102:9)",
      "    at listOnTimeout (node:internal/timers:588:17)",
      "    at processTimers (node:internal/timers:523:7)"
    ]
  }
}

Request: Please verify that my account’s task runner infrastructure has been properly provisioned after payment. This appears to be a backend issue that requires your team’s intervention.

Thank you for your urgent attention to this matter.

Best regards,

Tapan