My workflow stopped working after a token conflict, and a full reset doesn't help

Hello, I’m facing a critical issue with my n8n.cloud instance. My main, perfectly working workflow (Telegram + OpenAI Assistant) suddenly stopped functioning correctly. It triggers on the first message from a user, but never processes the second message. There are no errors in the execution logs. This happened after I duplicated the workflow and accidentally ran two active workflows with the same Telegram bot token. I have tried every possible solution to fix this, including: 1. Deleting the conflicting duplicate workflow. 2. Creating a completely new, separate Telegram bot with a new token. 3. Deleting the old Telegram credentials in n8n and creating new ones. 4. Revoking the bot token in BotFather and updating the credentials in n8n with the newly generated token. 5. Creating a brand new, simple test workflow from scratch. The problem persists even after all these steps. A key symptom I discovered is that even in a brand new workflow, the `$getWorkflowStaticData(‘global’)` function returns empty, which suggests that my instance is failing to persist static data between executions. My cloud instance URL is: `anton-vart.app.n8n.cloud` Could you please look into my instance? It seems like something is stuck on the backend. Thank you.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.