N8n Triggers become stale

Questions
1

Describe the problem/error/question

I have a few active n8n workflows that are tied to slack and Google drive that work great. However, when they are not triggered for a while (I don’t know the exact amount of time, but say multiple hours) they stop working. When I toggle them from active to inactive and then back to active they work great. How can I fix this?

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.84.3
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): I don’t know what this is
  • Running n8n via (Docker, npm, n8n cloud, desktop app): cloud
  • Operating system: cloud
2

Do you have an error workflow attached to monitor possible issues?

If not you may want to create one.

Here is a quite universal one. I created it to understand what’s going on with my triggers a while ago.

3

I don’t think it’s an error as there is nothing in the execution history. Once I toggle the active state off and on, execution works as normal.

1 Like
4

You cannot see trigger-level errors in execution logs exactly because execution wouldn’t be triggered.

Does it happen to Slack webhooks and Drive triggers only? I’ve never faced exactly this issue, but I would put a couple of sandboxes to test the triggers behaviour in isolation.

Just for the record, in my case where I used the error handler linked above it appeared that Google services were unaccessible once in a while. Not something that I could control but at least I was sure it wasn’t the issue with my other workflow malfunctioning.

If you are not really keen to digging into the possible cause, then you could build a scheduled workflow that would deactivate + activate workflows using n8n API.

Hope this helps.

2 Likes
5

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