Urgent Assistance Needed with Telegram Trigger Not Firing Simultaneously in Kubernetes n8n Setup

[Najmul_haq_Southun_n]

Dear n8n Team,

I hope you’re doing well. My name is Najmul Haq, and I’m currently managing multiple n8n projects hosted in Kubernetes clusters, each with its own board for different workflows. We’re facing a critical issue related to the Telegram trigger integration that is affecting our automation processes.

The Problem:

When both environments are activated simultaneously and we send a message from the respective Telegram bots for each project (different boards for different projects), no execution occurs in the workflows for either of the projects. This problem persists until we deactivate one of the projects, at which point:

1. We send a message from the active project’s Telegram bot, and the workflow does not execute.
2. After deactivating and reactivating the project, the message is finally received, and the corresponding workflow is triggered and executed as expected.

This issue occurs only when both projects are live and simultaneously receiving messages from their respective Telegram bots.

What We’ve Tried:

• Ensured that each project is using unique Telegram bot tokens and webhook URLs.
• Tried isolating the projects by activating one at a time, which works as expected.
• We’ve observed that even with one active project, the Telegram trigger doesn’t fire unless we deactivate and reactivate the project, after which the message is received and processed.
• No clear errors have been found in the logs, but the issue seems to relate to how n8n handles simultaneous triggers.

Request for Assistance:

Given the complexity of this setup with Kubernetes and multiple projects, we would appreciate your help in addressing the following:

1. Why is the Telegram trigger failing to fire when both projects are active simultaneously? Could this be a resource contention issue or a misconfiguration in n8n/Kubernetes?
2. What configurations can we adjust to prevent this behavior, ensuring that each project handles Telegram messages properly without interfering with the other?
3. Are there any specific settings or best practices we should follow when running multiple n8n projects in a Kubernetes environment to avoid such conflicts?
4. Could there be a deeper issue with how n8n is managing webhooks or triggers across multiple projects in the same environment?

This issue is critical for our ongoing projects and automation workflows, and your assistance would be invaluable in resolving it. We look forward to your guidance and support in troubleshooting this matter.

Thank you for your time and assistance.

Best regards,
Najmul Haq
Founder & CEO
Synerble | Justcallme

[Najmul_haq_Southun_n]

@bartv
Kindly support me

[BramKn]

Hi @Najmul_haq_Southun_n

Please do not randomly tag people.
If you need urgent help you should get a support contract with n8n or with a third party.
On the community forum it is community support and you have to be patient for someone to reply.
You cannot really ask for priority support without paying for a contract with SLA.

Also this seems more like a devops issue not perse n8n related. Selfhosting n8n is an advanced way of using n8n and complicating it with kubernetes was your own choice.
So you will need to make sure you have the expertise available to make sure stuff works and keeps working.