Error trigger not working

Hi everyone,

I have two workflows set up:

  1. Main workflow (Sajat-weboldal-agent) — an AI chatbot agent using a Chat Trigger, GPT-4o, Pinecone vector store, and Google Sheets tool. The errorWorkflow field is correctly set to the ID of my error workflow.

  2. Error workflow (Error-trigger-Sajat-weboldal) — starts with an Error Trigger node, followed by a Telegram node that should send a notification message when the main workflow fails.

The problem: When the main workflow fails during a production execution, the error workflow is never triggered and no Telegram notification is sent.

What I’ve already checked:

  • Both workflows are set to active: true

  • The errorWorkflow ID in the main workflow correctly points to the error workflow

  • The error workflow has a valid Error Trigger node connected to the Telegram node

  • I am testing with real production executions (not manual runs)

  • No Continue On Fail is set on any node

The setup looks correct to me, but the error workflow simply doesn’t fire. Has anyone experienced this with workflows hosted on Render? Could it be related to how Render handles long-running processes or WebSocket connections?

Any help appreciated!

Hi @Andras_Turnai good day!
From what you described, I’d first verify that the main workflow is really ending as a failed production execution. I’d add a Stop And Error node in the failing path of the main workflow to force a real production failure and confirm whether the Telegram error workflow fires, since that usually tells you whether the issue is the trigger setup or that the current error is being handled before it reaches the Error Trigger.

For me there is no result. I put an if and a Stop And Error node, but My error workflow still don’t get data. It is published and in the executions there is no new execution

@Andras_Turnai
when the error happens, are you triggering the workflow from the published chat/live trigger, or are you testing it manually inside the editor? I’m asking because the Error Trigger only runs for real automatic executions, not manual test runs.

@Andras_Turnai import this test workflow on your Render instance — it’s a schedule trigger into a Code node that just throws, with errorWorkflow pointed at your error workflow ID. activate it and wait for the cron to fire once. if the error workflow STILL doesn’t show a new execution, your Render instance is killing the process before the error routing completes, and you need to set RENDER_EXTERNAL_URL and keep the service alive with a healthcheck ping.

replace YOUR_ERROR_WORKFLOW_ID with the ID of your Error-trigger-Sajat-weboldal workflow, activate it, and check executions after 1 minute.