"send message and wait for response" telegram node hanging indefinitely

[gpundt456]

Describe the problem/error/question

I use "send message and wait for response" telegram nodes in one of my workflows with a custom form with a drop down of selections and a submit button. On the client side of telegram when the client tries to click submit on the form the submit button will hang indefinitely.

What is the error message (if any)?

There is no error message but this stops me from being able to use the workflow. I have tried inputting my issue into gemini 3 pro and it doesn't know what to do. It sounds like a webhook problem but I am sure I have correct webhooks in my .env and I have even used different ones that gemini told me to try and nothing has worked.

Please share your workflow/screenshots/recording

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

Share the output returned by the last node

Debug info

core

• n8nVersion: 2.2.4
• platform: npm
• nodeJsVersion: 22.17.0
• nodeEnv: undefined
• database: sqlite
• executionMode: regular
• concurrency: -1
• license: enterprise (production)

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/143.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2026-01-08T00:17:38.545Z}

[n8n-assistant]

Hey @gpundt456,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-6392".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-6392

[Raghav1428]

Hey! Thanks for reporting this 🙌

I’m trying to reproduce the issue locally but I’m missing a few details. Could you help with the following?

• A minimal workflow export (JSON) that reproduces the problem

• Exact steps to reproduce (from sending the Telegram message to clicking submit)

• Whether this still happens on the latest n8n version

• Any relevant Telegram setup details (bot type, chat type, custom form config)

This would help a lot in narrowing down whether this is a Telegram-specific issue, workflow config issue, or a regression.

Thanks!

[MookieLian]

@gpundt456 Thanks for reporting this issue! We've attempted to reproduce the problem, but unfortunately, we weren't able to replicate it. It's possible there was some environmental or other variable that prevented us from seeing the same behaviour.

If you're still encountering this issue, please provide any additional details or steps to reproduce it, and we'd be happy to investigate further. Thanks for your understanding!

Please upgrade to the latest stable version(2.4.6) of n8n, and let us know if you are still encountering this issue.

Reproduction: Docker on Debian, Self-hosted with worker/task runner, Version: 2.4.6, Database: Postgres, Queue mode

#closed:cant-reproduce