Error Workflow not triggering on timeout (n8n self hosted)

Questions
1

My Error Workflow is not triggering after my main workflow timesout. Even though I have a set up a max set up time and an Error Workflow.

I read somewhere that canceled workflows eventually turn into cancelled workflows but it has been more than 2 hours already and the workflows are still with status cancelled.

Can n8n currently handle this? Or is there a workaround anyone can think about?

Workflow Config:

image
image834×312 21 KB

Execution stops:

image
image513×166 7.84 KB

Error Workflow Executions: No execution

Information on your n8n setup

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

Yes seems like the execution will become canceled but will not trigger error workflow.

You can add as a feature request I guess.

However here is the solution that you can find thecanceled execution for specific workflow id

I think something not right. Because when filter status error : it didn’t contain canceled status.

You need to get all first and filter them out.