Trigger Nodes (Slack & Telegram) unreliable in production (cloud version)

Hi Guys, need some help here!

Issue:
I’m experiencing consistent reliability issues with both Slack and Telegram trigger nodes in production. I want to move to a paid plan but need to resolve this first.

Critical Observations:

  • No executions appear in execution logs during production runs
  • Only test executions are visible in logs
  • When pressing “Test” button, previous (missed) messages suddenly execute
  • This confirms messages are received but not processed in production

Details:

  • Both Slack and Telegram integrations are properly set up
  • Both work perfectly in test mode
  • In production, triggers are very inconsistent (mostly not working)
  • No rate limits hit
  • Webhooks and workflows are active
  • Sometimes messages trigger the workflow, but most times they don’t

Slack Setup:

  • Events API configured
  • Proper bot permissions/scopes
  • Event verification working
  • Channel selection working
  • Test mode: Works 100%
  • Production: Works ~20% of the time

Telegram Setup:

  • Webhook configured
  • Bot token set up correctly
  • Test mode: Works 100%
  • Production: Works ~20% of the time

What I’ve tried:

  • Double checking all permissions
  • Re-creating webhooks
  • Different channels/chats
  • Monitoring for rate limits
  • Ensuring workflows are active

Key Issues:

  1. Missing executions in production logs
  2. No error messages or failures logged
  3. Messages are received (proven by test button executing them later)
  4. Production triggers seem to be “sleeping” until test is pressed

I’ve spent considerable time troubleshooting and even used ChatGPT/Perplexity AI to verify my setup, but the core issue remains: triggers are unreliable in production while working perfectly in test mode.

Questions:

  1. Is this a known issue?
  2. Are there any workarounds?
  3. Would upgrading to a paid plan potentially fix this?
  4. Why do messages only execute when pressing test?

I’m eager to use n8n for business purposes but need reliable trigger functionality first.

Any help would be greatly appreciated!

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Technical Details:

  • n8n version: Cloud version (free trial)
  • Database: N/A (using cloud)
  • n8n EXECUTIONS_PROCESS: N/A (using cloud)
  • Running n8n via: n8n cloud
  • Operating system: N/A (using cloud)

Hey @Menno_Monet,

Welcome to the community :cake:

I think you opened a GitHub issue for this as well so we will be picking this up there, In the future please try to stick to one location so it doesn’t split the attention.