Telegram sendAndWait Node not working n8n on Railway

[jayray288]

I am new to n8n and learning the new Human in the loop capability by following youtube video by Leon Van Zyl. I am using Telegram sendandWait node to get user response. The workflow is sending the request for human input to Telegram correctly. However, on responding in Telegram, the node continues to wait. I tried to use Gmail sendandWait for human reponse which is giving the same result.

The output within the Telegram sendandWait node says 'Waiting for response even after the response was sent.

Details of the Telegram sendandWait node after response:

{
"nodes": [
{
"parameters": {
"operation": "sendAndWait",
"chatId": "={{ $('Telegram Trigger').item.json.message.chat.id }}",
"message": "={{ $json.output }}",
"approvalOptions": {
"values": {
"approvalType": "double"
}
},
"options": {}
},
"type": "n8n-nodes-base.telegram",
"typeVersion": 1.2,
"position": [
580,
0
],
"id": "c165f1c4-5790-44a1-907b-b42b466e6196",
"name": "Telegram",
"webhookId": "df087d5a-f4ac-4a3c-9f79-8a2b8aac34d9",
"credentials": {
"telegramApi": {
"id": "REMOVED FOR THIS POST",
"name": "Telegram account"
}
}
}
],
"connections": {},
"pinData": {},
"meta": {
"templateCredsSetupCompleted": true,
"instanceId": "aac07d8052135143ce708133c979fe660265e684c595fadd71b50a5ac7069f1a"
}
}

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

core

• n8nVersion: 1.78.1
• platform: docker (self-hosted)
• nodeJsVersion: 20.18.2
• database: postgres
• executionMode: scaling
• concurrency: -1
• license: community

storage

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

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

Generated at: 2025-02-17T12:33:17.148Z}

[Joffcom]

Hey @jayray288,

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

[jayray288]

I am pasting details of the error below:

Workflow Execution Error
Workflow: HITL Tutorial

Date and Time: 2025-02-18T10:26:12.968+05:30

Last Node Executed:

Error Detail:

No node to start the workflow from could be found
Stack Trace:

Error: No node to start the workflow from could be found
at Queue.onFailed (/usr/local/lib/node_modules/n8n/node_modules/bull/lib/job.js:516:18)
at Queue.emit (node:events:518:28)
at Object.module.exports.emitSafe (/usr/local/lib/node_modules/n8n/node_modules/bull/lib/utils.js:50:20)
at EventEmitter.messageHandler (/usr/local/lib/node_modules/n8n/node_modules/bull/lib/queue.js:476:15)
at EventEmitter.emit (node:events:518:28)
at DataHandler.handleSubscriberReply (/usr/local/lib/node_modules/n8n/node_modules/ioredis/built/DataHandler.js:80:32)
at DataHandler.returnReply (/usr/local/lib/node_modules/n8n/node_modules/ioredis/built/DataHandler.js:47:18)
at JavascriptRedisParser.returnReply (/usr/local/lib/node_modules/n8n/node_modules/ioredis/built/DataHandler.js:21:22)
at JavascriptRedisParser.execute (/usr/local/lib/node_modules/n8n/node_modules/redis-parser/lib/parser.js:544:14)
at Socket. (/usr/local/lib/node_modules/n8n/node_modules/ioredis/built/DataHandler.js:25:20)
at Socket.emit (node:events:518:28)
at addChunk (node:internal/streams/readable:561:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
at Socket.Readable.push (node:internal/streams/readable:392:5)
at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
This is an automated message from your workflow system.

[Joffcom]

Hey @jayray288

It sounds like it could be a configuration issue but first... does it work if you don't use the test option and just make the workflow active and try from there?

[jayray288]

I tried to switch the flow to active - but that didn't work. I tried the flow on render. I set up n8n with the environment variable NODE_VERSION = 22. This worked for the render platform. Jay

…

On Fri, Feb 21, 2025 at 5:54 AM Jon ***@***.***> wrote: Hey @jayray288 <https://github.com/jayray288> It sounds like it could be a configuration issue but first... does it work if you don't use the test option and just make the workflow active and try from there? — Reply to this email directly, view it on GitHub <#13331 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJD732HYS6J4FI4Z66QJU32QZW5RAVCNFSM6AAAAABXKTYJ2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZTGAZDEMBWGI> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: Joffcom]*Joffcom* left a comment (n8n-io/n8n#13331) <#13331 (comment)> Hey @jayray288 <https://github.com/jayray288> It sounds like it could be a configuration issue but first... does it work if you don't use the test option and just make the workflow active and try from there? — Reply to this email directly, view it on GitHub <#13331 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJD732HYS6J4FI4Z66QJU32QZW5RAVCNFSM6AAAAABXKTYJ2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZTGAZDEMBWGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Joffcom]

Hey @jayray288

Changing that option shouldn't change anything but if anything I would have expected it to cause errors.

As it is working though I will mark this as solved for now.