telegram trigger hangs forever

[SavostinVladimir]

Describe the problem/error/question

The Telegram Trigger node fails with error. And after that I guess it retry with invalid message forever

What is the error message (if any)?

{ "ok": false, "error_code": 400, "description": "Bad Request: file is too big" }

NodeApiError: Bad request - please check your parameters at WebhookContext.apiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Telegram/GenericFunctions.js:115:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WebhookContext.webhook (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Telegram/TelegramTrigger.node.js:246:52) at WebhookService.runWebhook (/usr/local/lib/node_modules/n8n/dist/webhooks/webhook.service.js:181:16) at Object.executeWebhook (/usr/local/lib/node_modules/n8n/dist/webhooks/webhook-helpers.js:157:33)

Please share your workflow/screenshots/recording

Debug info

core

• n8nVersion: 1.74.3
• platform: cloud
• license: pro

storage

• success: all
• error: all
• progress: true
• manual: true

pruning

dont know

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/131.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2025-01-21T18:49:15.304Z}

[Joffcom]

Hey @SavostinVladimir,

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

[Joffcom]

Hey @SavostinVladimir

It looks like this issue is with the size of the file as the error suggests.

How big is the file that was sent to the channel?

[SavostinVladimir]

Hey @Joffcom that was a video 22 MB. I've already seen the ticket https://community.n8n.io/t/large-file-download-for-telegram/35474

But I need some workaround, I mean, how can I skip such message? Because n8n retries failed workflows again and again, as I see

[Joffcom]

Hey @SavostinVladimir

We should probably add an option for that, the best option for now would be to not download the files automatically then see if they can be downloaded in a later node once you have checked the sizes.