Telegram Trigger Delay Issue

[Anshul_Namdev]

Hi @oduvanekb Welcome!
I felt that kind of issue with telegram & slack, what i have done is EXECUTIONS_PROCESS=main in my env variable, so that all my flows production executions run in the main process eliminating that sleep behavior or a slight delay, it is worth giving a try. See this:

@theJoshMuller

This environment variable controls how the execution process is managed. It has a few settings, but the one that might help you is main.

By setting EXECUTIONS_PROCESS=main, you eliminate the inter-process communication and potential for serialization/deserialization issues that might be at the heart of this bug. It essentially makes your n8n instance run as a single, monolithic process.

The error seems to happen when the main process hands off the workflow to a worker process. In that handoff, the AI Agent node’s definition is somehow lost or corrupted because the Telegram Trigger is also present. By forcing the execution to stay in the main process, you skip this handoff entirely. The process that loaded the workflow from the database is the same one that will execute it, which should prevent the node definition from getting lost.