Try to activate workflow error

Questions
1

Good afternoon.
I have a Telegram assistant bot that interacts with clients. During outages, there’s often a surge of incoming messages, and to prevent the request queue from growing, I considered switching to multi-threaded (queue) mode.

However, after enabling queue mode, the assistant’s workflow stopped activating, showing the following errors:

Activation of workflow “(AlexPan) Ассистент @OpticInetBot 00” (Bnpl3qRMCFb5mKqM) did fail with error: “Bad request - please check your parameters” | retry in 128 seconds
Activation of workflow “(AlexPan) Ассистент @OpticInetBot 00” (Bnpl3qRMCFb5mKqM) did fail with error: “The service is receiving too many requests from you” | retry in 128 seconds
Try to activate workflow “(AlexPan) Ассистент @OpticInetBot 00” (Bnpl3qRMCFb5mKqM)

All other workflows continue to work normally.

Has anyone encountered this issue before? And will using queue mode actually help the bot handle high loads more effectively?

2

Hi, @isakovalishka !

This happens because, in queue mode, multiple n8n processes try to register the Telegram webhook at the same time. Telegram doesn’t allow this, so activation fails with “Bad request” and “Too many requests”. Other workflows work because they don’t use the Telegram Trigger.

The recommended solution is not to use queue mode for Telegram Trigger workflows. Keep the trigger on a single main instance and use queue mode only for downstream processing after the message is received.

If needed, temporarily disable queue mode, activate the workflow, and then re-enable queue mode only for non-trigger workflows.