Telegram trigger just stopped working overnight

**Fixed it by restarting the workspace in the admin panel **

I had a really nice workflow working, using telegram as a trigger. It worked last night and today when I went to show somebody its just completely stopped working.

First it wouldn’t recognise any messages and wouldn’t trigger. So I thought to delete the credentials and add them in again new. That didnt work, so I made a new bot all together. Now whenever I create a new bot on telegram and enter the credentials, I get a notification in the bottom right saying “Node has no access to credentials” and

Problem running workflow
Credential with ID "y8O*****T6YrTQ" does not exist for type “telegramApi”.

The only thing I can say I have done that may have affected this is create a new workflow and also used a telegram node as the trigger, although I hadnt entered in any credentials for it as I was yet to set up a new bot.

The credentials that I am trying to use are 100% within the scope of the project, I am inside of the project when I create them and they then get listed along side just the other credentials in my project.

Please can somebody help me this is really frustrating, I was due to show my boss this.

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

hi @liamrourke

Reading your first sentence looks like you got this working?