I’m experiencing inconsistent behavior with my Telegram trigger in N8N (Starter Monthly online subscription). The workflow is set to active, but it doesn’t always respond to Telegram messages. When I toggle the workflow’s active button, it appears to process any messages that were received while it wasn’t actively listening. I’d appreciate any insights into what might be causing this.
Version - 1.85.4 (Latest Stable)
Platform - N8N cloud
You can check your executions to see when it’s being triggered.
Test executions have a little “lab” icon
And the Telegram trigger actually retrieves previously received messages when you run a test execution. But when the workflow is active/in production it works by only receiving future messages.
If my reply answers your question, please remember to mark it as a solution.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
