N8n Cloud instance frozen - Webhooks failing and Executions not saving

Questions
1

Describe the problem/error/question:
My n8n Cloud instance (correaatibaia.app.n8n.cloud) seems completely frozen at the infrastructure level. For the past 3 days, all workflows have stopped working. Webhook nodes are rejecting incoming POST requests instantly (returning 0ms configuration errors). Even worse, the “Executions” registry is not persisting or saving any logs at all, and all other independent workflows in this account are also dead. It looks like a database deadlock or a stuck queue on the cloud server side.
What is the error message (if any)?
“Nó ‘Responder ao Webhook’ não utilizado encontrado no fluxo de trabalho” / WorkflowConfigurationError: Unused Respond to Webhook node found in the workflow. (Even when the node is correctly routed or bypassed, the instance fails to log or persist any execution).
Information on your n8n setup:

  • n8n version: 2.27.4 (Cloud)
  • Running n8n via: n8n cloud
  • Operating system: Cloud Instance
2

Hi @Silvio_Correa Welcome!
This reads like a workflow config error, not an infra freeze, that error is what’s rejecting the webhook instantly (your 0ms) and stopping the run from being saved. Open the Webhook node and change Respond from Immediately to Using 'Respond to Webhook' node, then make sure the Respond to Webhook node sits on the executed path as the last node.
See this:

If the other workflows and execution logging are still dead across the whole account after that fix, that part is Cloud-side, contact help@n8n.io so they can check your instance.

4

​"Hi Silvio, I’ve seen this behavior before. While the moderator’s suggestion to check the ‘Response Mode’ is technically correct, it often doesn’t resolve the underlying issue if you’re dealing with a stalled backend queue on n8n Cloud or a database deadlock causing those 0ms rejections.
​If you’ve already patched your ‘Respond to Webhook’ nodes and the execution logs are still not persisting, you’re likely facing an infrastructure-level sync issue that a simple redeploy won’t fix. I specialize in n8n production troubleshooting and can audit your workflow structure and backend logs to identify if this is a configuration error or a genuine service-side deadlock.
​If you’re still stuck, feel free to DM me – I can jump in and help you get your production back online today."