🐛 Bug Report: Telegram agent stops replying after several messages while conversation remains ACTIVE

[ANSHSINGH050404]

📜 Description

Telegram agent conversations work initially, but after several messages a later message is silently ignored. The conversation remains ACTIVE, Telegram receives no response, and no user-facing error is shown.

👟 Reproduction steps

1. Configure a Novu agent with Telegram.
2. Send several messages to the Telegram bot.
3. Confirm the agent replies normally.
4. Send another message, for example: hii.
5. Observe that no reply is sent.
6. Check the conversation status.

👍 Expected behavior

Every valid Telegram message should be processed and receive an agent response, or the user should receive a clear error/fallback message.

👎 Actual Behavior with Screenshots

Novu version

Novu SaaS

npm version

NA

node version

NA

📃 Provide any additional context for the Bug.

Static code tracing identified several possible failure points:

• Telegram starts message processing without awaiting it before returning 200 OK.
• Chat SDK uses a default drop-on-lock-conflict strategy.
• Lock conflicts and runtime errors are logged but do not produce a fallback Telegram reply.
• The Chat SDK lock TTL is 30 seconds, which may be shorter than an LLM/tool execution.
• Managed provider and queue-ready failures may be swallowed without retry or user notification.
  Relevant area: Telegram webhook handling, Chat SDK conversation locking, managed runtime dispatch, and provider error handling.

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to submit PR?

Yes I am willing to submit a PR!

[linear-code]

NV-8528

[ANSHSINGH050404]

@scopsy, could you please check whether you can reproduce this issue on your side? The attached screenshot shows the behavior I’m seeing.