Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Telegram Trigger returns stale data on second manual test run in editor [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28378•Fetched 2026-04-13 05:45:18
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Ember-DawnEmber-Dawn
Participants
Ember-DawnEmber-Dawnn8n-assistant[bot]n8n-assistant[bot]
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

Error Message

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

  • I found a regression in the Telegram Trigger test behavior.

  • This happens when testing an unpublished workflow from the editor.

  • In n8n 1.109.1:

    • The Telegram Trigger works as expected.
    • On the 2nd, 3rd, and later manual test runs, it keeps listening.
    • It only finishes after I send a new Telegram message.
    • It returns the latest message.

  • In n8n 2.14.2:

    • The first manual test run works correctly.
    • But the 2nd and later manual test runs are wrong.
    • The Telegram Trigger starts listening and then ends almost immediately.
    • It returns the message from the first test run.
    • It does not wait for a new Telegram message.
    • It returns stale data.

  • This looks like cached trigger data or a stale listener state being reused across manual test runs.

To Reproduce

  • Create a new workflow.

  • Do not publish / activate it.

  • Add a Telegram Trigger node.

  • Configure the Telegram bot credentials correctly.

  • Click Run workflow in the editor.

  • Send a message to the bot from the Telegram client.

  • Confirm that the trigger receives the message.

  • Then test again:

    • Click Run workflow a second time.
    • Do not change the node.
    • Send a new message from the Telegram client.

  • In n8n 2.14.2:

    • The trigger stops almost immediately.
    • It returns the message from the first run.
    • It does not wait for the new message.

  • Repeat a third time.

  • The same issue happens again.

Expected behavior

  • Every manual test run should start a fresh listener.
  • The Telegram Trigger should wait for a new Telegram message.
  • It should not finish immediately.
  • It should not reuse data from a previous manual test run.
  • The 2nd, 3rd, and later runs should behave the same as the 1st run.

Debug Info

Debug info

core

  • n8nVersion: 2.14.2
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.13.1
  • nodeEnv: production
  • database: postgres
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: abb46dd7-ec61-419a-a1e2-ff70adc057f4

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/146.0.0.0 safari/537.36 edg/146.0.0.0
  • isTouchDevice: false

Generated at: 2026-04-13T00:34:39.315Z

Operating System

Ubuntu 24.04 LTS

n8n Version

2.14.2

Node.js Version

24.13.1

Database

PostgreSQL

Execution mode

main (default)

Hosting

n8n cloud

extent analysis

TL;DR

The issue can be mitigated by resetting the Telegram Trigger node or the workflow before each manual test run to prevent stale data reuse.

Guidance

  • Verify that the Telegram Trigger node is properly configured and that the bot credentials are correct to ensure the issue is not related to authentication.
  • Try resetting the workflow or the Telegram Trigger node before each manual test run to see if it resolves the issue of stale data being returned.
  • Check if there are any caching mechanisms in place that could be causing the trigger to reuse data from previous runs and consider disabling them for manual test runs.
  • Consider downgrading to n8n 1.109.1 temporarily to confirm if the issue is version-specific.

Example

No code snippet is provided as the issue seems related to the workflow editor and node configuration rather than code.

Notes

The exact cause of the issue is unclear, but it appears to be related to how n8n 2.14.2 handles the state of the Telegram Trigger node across manual test runs. Further investigation into the differences between n8n 1.109.1 and 2.14.2 may be necessary.

Recommendation

Apply workaround: Reset the Telegram Trigger node or the workflow before each manual test run. This approach is chosen because it directly addresses the symptom of stale data reuse without requiring a version downgrade or code changes.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

  • Every manual test run should start a fresh listener.
  • The Telegram Trigger should wait for a new Telegram message.
  • It should not finish immediately.
  • It should not reuse data from a previous manual test run.
  • The 2nd, 3rd, and later runs should behave the same as the 1st run.
#generation error#database connection#vector store#embedding generation#cache error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING