Dear Latenode Support Team,
I am writing to report a persistent “system error” in my workflow (Workflow Title: Асистент для РОПів, Scenario URL: https://app.latenode.com/scenarios/683c4e85d7a848642232fefa) specifically in the #4 Telegram / New Updates (Instant) node.
The workflow shows intermittent functionality:
- The
/startcommand is processed correctly by node #4. - After recent troubleshooting, the bot briefly started responding to regular text messages (via node #16), but the generated data was incorrect (“null” or irrelevant information).
- However, after one or two such interactions, the workflow again returns to a “system error” in node #4 for subsequent regular messages, halting execution entirely.
The error message I receive from Latenode is a generic “system error” with no further details or stack trace provided in the logs for node #4.
I have already taken the following troubleshooting steps:
- “Allowed Updates” in node #4: I attempted to correct the “Allowed Updates” setting in node #4. It currently displays
message message, and I am unable to change or remove this value in the UI by clicking “X” or selectingmessagefrom the dropdown suggestions. This suggests a potential UI bug or backend issue preventing proper configuration of the trigger. - Re-established Telegram bot connection: I have regenerated the bot token via BotFather and created a new, uniquely named connection in Latenode, ensuring it’s the only active Telegram authorization in my account.
- “Max Tokens” in node #15: Confirmed that “Max Tokens” in node #15 is set to a valid value (e.g., 350) and not 0.
Given the intermittent functionality and the inability to properly configure the “Allowed Updates” field in node #4, I suspect there might be:
- A deeper issue with how Latenode’s Telegram trigger handles specific message content, possibly due to an invalid
Allowed Updatessetting that I cannot change. - An underlying webhook conflict that manifests intermittently.
- A bug within the Latenode platform itself that prevents detailed error logging for this specific issue.
Could you please assist me in diagnosing and resolving this persistent “system error” in the Telegram trigger node? The inability to modify the “Allowed Updates” field is particularly concerning and may be directly contributing to this problem.
Thank you, [Andrew / Email: [email protected]]
