My credentials keep getting messed up. I have a webhook node → basic auth.
It works, and then it suddenly doesn’t. (authorization error).
When i de-activate and re-activate the workflow, it works again and i get a “workflow has started” reply in my test.
This problem has repeated a few times in the last 7 days. The credentials (url, user, pass) were never changed.
I’m using n8n cloud.
I’m facing an issue where the triggers in my n8n workflows are not firing, even though the workflows are active.
The webhooks are not being received unless I deactivate the workflow and run it manually. When I do that, it works fine for a short period, but then it stops triggering again once the workflow is active.
even the native telegram triggers
The Telegram triggers stop firing even though the workflow remains active. When I deactivate and manually execute the workflow, it starts working again for a while but eventually stops triggering automatically.
Hi @skpwrz
This is a known issue that can happen on n8n Cloud.
The fact that deactivating and reactivating the workflow temporarily fixes the problem is the key clue. It means your credentials are correct, but the active workflow is losing its connection to them.
The likely cause is a background restart or update on your cloud instance. When this happens, the workflow’s “session” can be interrupted, causing the credential error. Reactivating it forces a fresh, successful connection.
Since you cannot control this, the only solution is to contact n8n Cloud support.
They can check the server logs for your instance and provide a permanent fix. This isn’t something you can solve on your own.
If you found this answer helpful, please consider marking it as the solution and giving it a like .
Hi @Websensepro , thanks for the reply.
What is the best way to contact n8n cloud support? I’m only getting AI messages.