Erronuous execution loop in my workflows

[User1_Development]

Describe the problem/error/question

Hey, I am getting a serious problem in my n8n workflows, let me just give a brief context: I am using a hosted n8n which is hosted on cloud run. It basically handles the automatic messaging infrastructure for a health based organization.

PROBLEM: If due to any reason in any of the node an error occurs my workflow’s execution fails/stops but the thing is even after the execution of the same workflow is successful in the consequent execution that failed execution keeps repeating itself again and again after a specific period of time. I have used a error workflow to see the reason for failure and mostly the errors were because of the connection timeout with my cloudsql hosted postgresql db, so I fixed it with adding limited retries and a fixed timeout of 120sec and that resolved it, but the issue is those failed execution are still somehow executing.

P.S.: I have tried clearing the execution_entity table multiple times and also this:
”UPDATE execution_entity SET status = ‘error’, “stoppedAt” = NOW() WHERE status = ‘new’ OR status = ‘running’;”

But no effect.

What is the error message (if any)?

No Error message

Please share your workflow

(Select 

the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

• n8n version: 1.50.1
• Database: Postgres
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via : gcp-cloudrun
• Operating system:

[Orionpax]

@User1_Development Based on your description of the problem, the issue you’re experiencing, failed executions automatically retrying, is likely not a n8n feature but a symptom of an infrastructure problem. This is often linked to processes running in “queue mode” being interrupted and not shutting down cleanly, causing the system to re attempt them.

[User1_Development]

Thanks @Orionpax , but I did checked my infrastructure by going through my YAML configuration file for this n8n service, but found nothing.

[User1_Development]

I just found out what the actual issue was, it was response feedback issue actually, my webhook was getting triggered again and again by an external service because the error in any node was not sending any response back as I had kept the respond to webhook node at last which was preventing any status response back so now I have kept it immediately after my webhook trigger and now it has resolved.