Hello n8n team, I’m experiencing a critical bug with the Telegram node on n8n Cloud that seems to be related to execution context. **Environment:** * n8n Version: 1.107.4 (Cloud) **Workflow Goal:** A Telegram bot for time tracking using Supabase. 1. On `/start`, if a user is new, the workflow creates them in Supabase and sends a welcome message (“Ask Name”). 2. The user replies with their name. A second workflow execution is triggered. It updates the user’s name in Supabase and should send a second message (“Ask Rate”). **The Bug:** * The first execution (new user registration) works **perfectly**. The “Ask Name” Telegram node successfully sends a message. * The second execution (handling the name reply) **fails**. The Supabase `update` operation works correctly, but the final Telegram node (“Ask Rate”) fails with a `400 Bad Request: chat not found` error from the Telegram API. **What I have already done to debug:** * Confirmed the `Chat ID` expression is correct and resolves to the right number in the failing node. * Confirmed the bot is NOT blocked by the user (I have performed a full delete/block/unblock/restart of the chat in Telegram). * Completely revoked and re-issued the Telegram Bot Token via BotFather and created new credentials in n8n. * Confirmed RLS is disabled in Supabase. * The most important test: I **cloned the working Telegram node** from the successful first branch and put it on the failing second branch. The clone fails with the exact same error. This proves the node configuration is correct, but the execution context is somehow causing the issue. This is not a workflow logic error. It seems to be a bug where the Telegram API call fails consistently only on a second, separate execution instance. Here is the full error log from the failing node:
{
“errorMessage”: “Bad request - please check your parameters”,
“errorDescription”: “Bad Request: chat not found”,
“errorDetails”: {
“rawErrorMessage”: [
“400 - {"ok":false,"error_code":400,"description":"Bad Request: chat not found"}”
],
“httpCode”: “400”
},
“n8nDetails”: {
“nodeName”: “Send a text message1”,
“nodeType”: “n8n-nodes-base.telegram”,
“nodeVersion”: 1.2,
“resource”: “message”,
“operation”: “sendMessage”,
“time”: “8/29/2025, 9:20:51 PM”,
“n8nVersion”: “1.107.4 (Cloud)”,
“binaryDataMode”: “filesystem”,
“stackTrace”: [
“NodeApiError: Bad request - please check your parameters”,
" at ExecuteContext.apiRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_1af219c3f47f2a1223ec4ccec249a974/node_modules/n8n-nodes-base/nodes/Telegram/GenericFunctions.ts:230:9)“,
" at processTicksAndRejections (node:internal/process/task_queues:105:5)”,
" at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_1af219c3f47f2a1223ec4ccec249a974/node_modules/n8n-nodes-base/nodes/Telegram/Telegram.node.ts:2193:21)“,
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_0c275070fd0434c00ffd62213b2bcae4/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1212:9)”,
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_0c275070fd0434c00ffd62213b2bcae4/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1582:27",
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_0c275070fd0434c00ffd62213b2bcae4/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2158:11"
]
}
}