Canceled Executions, even though not EXECUTIONS_TIMEOUT set

Questions
1

Problem

We recently updated n8n from 1.5.1 to 1.42.2. Since then some executions are set to status canceled instead of failed.
This is a problem, since canceled executions can not be retried.

Question

Does anyone know what could cause this and how to stop executions from ending up in status canceled?

Information on your n8n setup

  • n8n version:: 1.42.1
  • Database (default: SQLite): postgresql
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • n8n EXECUTIONS_MODE: queue
  • Running n8n via (Docker, npm, n8n cloud, desktop app): k8s docker
  • Operating system: linux

We have neither set EXECUTIONS_TIMEOUT nor EXECUTIONS_TIMEOUT_MAX.

1 Like
2

Hi @tillwestpfahl

Thanks for posting here and welcome to the community! :cupcake:

Could you please share a bit more context, do you have screenshots? Is this related to particular workflows? Since you are using queue mode, did you also update your workers?

3

Hi @ria,

thanks for the reply. Yes we have updated our workers.
I cannot provide further context. Since this post, we have not had any other canceled executions, so it might have been an unfortunate one time thing. If it happens again, I will post a reply here with more context.

2 Likes
4

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