Hi @tridi, thanks for sharing that. We’ve seen a few mentions in the past about timeout issues around Telegram. Often it seems like it has been a configuration issue, but if you are running two installations simultaneously with identical configurations other than the version then that might point to something different.
You said your second instance was upgraded from 1.44.1 - did you encounter this issue prior to the upgrade to 1.46 at any time?
If not, have you seen timeouts occurring with other nodes on your 1.46 instance?
This should help us understand if the issue is due to configuration, the change released in 1.43, or a later change made that would impact more nodes than just Telegram.
Previously, I upgraded to version 1.42.2 first because I saw on another thread about a similar issue but it applied to the majority of nodes whereas I only had credential errors on the Telegram node.
However, because the error persisted in version 1.42.2, I tried upgrading again to version 1.46.0 and the result was the same, which is an error when adding credentials to the Telegram node and there were no similar errors in other nodes that I use most often such as Jira, Trello, HTTP request (Only error for telegram API), Facebook Graph, WordPress, and others.
I have also tried a new n8n installation and the result remains the same if the version is set to “latest” or above version “1.42.1” so the current solution is only safe if I install on version 1.42.1. Unfortunately, this does not apply to installations that have already experienced errors because even though I have already deleted the old Docker image, the error still persists. So, the solution is to only backup the workflow and temporarily move it to a new installation in version 1.42.1.
continue on this thread if anyone else have this problem to find the solution from @netroy and thanks to @Ludwig for the response and follow up for this issue
