Telegram triger doesnt work at all

[JohnnyMotoboy]

Telegram Triger stopped working all of sudden. I have not changed any settings . It's just indicating that it is listening to events, I send a message to telegram on the phone to check work flow , but telegram trigger node doesnt read it, but it was working fine, and like I said I have not changes any settings. I tried to stop and pressed "stop listening" but the button didn't work at all, it kept on listening. That's frustrating, I was about to lunch this project . I checked everything with telegram app, especialy my bot, no settings were changed since it was created, so the problem must be in n8n. Because as I was testing workflows it was working and respind fine.

What is the error message (if any)?

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.)

Share the output returned by the last node

Debug info

core

• n8nVersion: 1.75.3
• platform: npm
• nodeJsVersion: 20.18.2
• database: sqlite
• executionMode: regular
• concurrency: 5
• license: community

storage

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

pruning

• enabled: true
• maxAge: 168 hours
• maxCount: 2500 executions

client

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

Generated at: 2025-02-20T10:12:38.487Z}

[Joffcom]

Hey @JohnnyMotoboy,

We have created an internal ticket to look into this which we will be tracking as "GHC-903"

[JohnnyMotoboy]

it says "Problem running workflow" Cannot read properties of undefined (reading disabled)

[Joffcom]

Hey @JohnnyMotoboy,

Did you happen to have the workflow active while testing it? That can cause issues with Telegram as a bot is only allowed to use one url at a time for webhooks and the test would overwrite it so you need to disable then activate the workflow again.

When you get the problem running message does it appear on a certain node as well?

[JohnnyMotoboy]

No , i always kept it on test mode . Never active чт, 20 февр. 2025 г., 17:31 Jon ***@***.***>:

…

Hey @JohnnyMotoboy <https://github.com/JohnnyMotoboy>, Did you happen to have the workflow active while testing it? That can cause issues with Telegram as a bot is only allowed to use one url at a time for webhooks and the test would overwrite it so you need to disable then activate the workflow again. When you get the problem running message does it appear on a certain node as well? — Reply to this email directly, view it on GitHub <#13385 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5T7E5HB2U5QMLD3DRBD4JL2QXDJRAVCNFSM6AAAAABXQMF6EWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRGM3DEMBZGA> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: Joffcom]*Joffcom* left a comment (n8n-io/n8n#13385) <#13385 (comment)> Hey @JohnnyMotoboy <https://github.com/JohnnyMotoboy>, Did you happen to have the workflow active while testing it? That can cause issues with Telegram as a bot is only allowed to use one url at a time for webhooks and the test would overwrite it so you need to disable then activate the workflow again. When you get the problem running message does it appear on a certain node as well? — Reply to this email directly, view it on GitHub <#13385 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5T7E5HB2U5QMLD3DRBD4JL2QXDJRAVCNFSM6AAAAABXQMF6EWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRGM3DEMBZGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[JohnnyMotoboy]

Then I opened up another workflow, and I created another telegram bot and tried to activate it and it was working perfectly, but my main workflow didn't work at all чт, 20 февр. 2025 г., 17:41 Johnny Reynn ***@***.***>:

…

No , i always kept it on test mode . Never active чт, 20 февр. 2025 г., 17:31 Jon ***@***.***>: > Hey @JohnnyMotoboy <https://github.com/JohnnyMotoboy>, > > Did you happen to have the workflow active while testing it? That can > cause issues with Telegram as a bot is only allowed to use one url at a > time for webhooks and the test would overwrite it so you need to disable > then activate the workflow again. > > When you get the problem running message does it appear on a certain node > as well? > > — > Reply to this email directly, view it on GitHub > <#13385 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/A5T7E5HB2U5QMLD3DRBD4JL2QXDJRAVCNFSM6AAAAABXQMF6EWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRGM3DEMBZGA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > [image: Joffcom]*Joffcom* left a comment (n8n-io/n8n#13385) > <#13385 (comment)> > > Hey @JohnnyMotoboy <https://github.com/JohnnyMotoboy>, > > Did you happen to have the workflow active while testing it? That can > cause issues with Telegram as a bot is only allowed to use one url at a > time for webhooks and the test would overwrite it so you need to disable > then activate the workflow again. > > When you get the problem running message does it appear on a certain node > as well? > > — > Reply to this email directly, view it on GitHub > <#13385 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/A5T7E5HB2U5QMLD3DRBD4JL2QXDJRAVCNFSM6AAAAABXQMF6EWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRGM3DEMBZGA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[JohnnyMotoboy]

The second telegram bolt was working perfectly, and it was listening to my events . When they press the listen to events on the main workflow and I tried to stop but I pressed the button stop and it didn't stop until I reload the page. чт, 20 февр. 2025 г., 17:41 Johnny Reynn ***@***.***>:

…

Then I opened up another workflow, and I created another telegram bot and tried to activate it and it was working perfectly, but my main workflow didn't work at all чт, 20 февр. 2025 г., 17:41 Johnny Reynn ***@***.***>: > No , i always kept it on test mode . Never active > > чт, 20 февр. 2025 г., 17:31 Jon ***@***.***>: > >> Hey @JohnnyMotoboy <https://github.com/JohnnyMotoboy>, >> >> Did you happen to have the workflow active while testing it? That can >> cause issues with Telegram as a bot is only allowed to use one url at a >> time for webhooks and the test would overwrite it so you need to disable >> then activate the workflow again. >> >> When you get the problem running message does it appear on a certain >> node as well? >> >> — >> Reply to this email directly, view it on GitHub >> <#13385 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/A5T7E5HB2U5QMLD3DRBD4JL2QXDJRAVCNFSM6AAAAABXQMF6EWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRGM3DEMBZGA> >> . >> You are receiving this because you were mentioned.Message ID: >> ***@***.***> >> [image: Joffcom]*Joffcom* left a comment (n8n-io/n8n#13385) >> <#13385 (comment)> >> >> Hey @JohnnyMotoboy <https://github.com/JohnnyMotoboy>, >> >> Did you happen to have the workflow active while testing it? That can >> cause issues with Telegram as a bot is only allowed to use one url at a >> time for webhooks and the test would overwrite it so you need to disable >> then activate the workflow again. >> >> When you get the problem running message does it appear on a certain >> node as well? >> >> — >> Reply to this email directly, view it on GitHub >> <#13385 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/A5T7E5HB2U5QMLD3DRBD4JL2QXDJRAVCNFSM6AAAAABXQMF6EWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRGM3DEMBZGA> >> . >> You are receiving this because you were mentioned.Message ID: >> ***@***.***> >> >

[JohnnyMotoboy]

For some reason, the website pinned the Telegram trigger. And I don't know why then I unpin it and try to run again and again, same isue appeared чт, 20 февр. 2025 г., 17:42 Johnny Reynn ***@***.***>:

…

The second telegram bolt was working perfectly, and it was listening to my events . When they press the listen to events on the main workflow and I tried to stop but I pressed the button stop and it didn't stop until I reload the page. чт, 20 февр. 2025 г., 17:41 Johnny Reynn ***@***.***>: > Then I opened up another workflow, and I created another telegram bot and > tried to activate it and it was working perfectly, but my main workflow > didn't work at all > > чт, 20 февр. 2025 г., 17:41 Johnny Reynn ***@***.***>: > >> No , i always kept it on test mode . Never active >> >> чт, 20 февр. 2025 г., 17:31 Jon ***@***.***>: >> >>> Hey @JohnnyMotoboy <https://github.com/JohnnyMotoboy>, >>> >>> Did you happen to have the workflow active while testing it? That can >>> cause issues with Telegram as a bot is only allowed to use one url at a >>> time for webhooks and the test would overwrite it so you need to disable >>> then activate the workflow again. >>> >>> When you get the problem running message does it appear on a certain >>> node as well? >>> >>> — >>> Reply to this email directly, view it on GitHub >>> <#13385 (comment)>, >>> or unsubscribe >>> <https://github.com/notifications/unsubscribe-auth/A5T7E5HB2U5QMLD3DRBD4JL2QXDJRAVCNFSM6AAAAABXQMF6EWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRGM3DEMBZGA> >>> . >>> You are receiving this because you were mentioned.Message ID: >>> ***@***.***> >>> [image: Joffcom]*Joffcom* left a comment (n8n-io/n8n#13385) >>> <#13385 (comment)> >>> >>> Hey @JohnnyMotoboy <https://github.com/JohnnyMotoboy>, >>> >>> Did you happen to have the workflow active while testing it? That can >>> cause issues with Telegram as a bot is only allowed to use one url at a >>> time for webhooks and the test would overwrite it so you need to disable >>> then activate the workflow again. >>> >>> When you get the problem running message does it appear on a certain >>> node as well? >>> >>> — >>> Reply to this email directly, view it on GitHub >>> <#13385 (comment)>, >>> or unsubscribe >>> <https://github.com/notifications/unsubscribe-auth/A5T7E5HB2U5QMLD3DRBD4JL2QXDJRAVCNFSM6AAAAABXQMF6EWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZRGM3DEMBZGA> >>> . >>> You are receiving this because you were mentioned.Message ID: >>> ***@***.***> >>> >>

[Joffcom]

Hey @JohnnyMotoboy

If the workflow is not active then the node wouldn't listen so I would expect that to fail.

If you press the listen button to test the workflow it would only work the once, are you self hosting or using cloud and have you checked the telegram bot to see which webhook url is registered?