Workflow error - No active execution found

[Vadorequest]

Describe the problem/error/question

A workflow which I haven’t updated recently and was working fine for months, just stopped working today at 11PM, throwing No active execution found.

The trigger is a cron, that runs every 5s, using */5 * * * * *.

When running the workflow manually, it executes just fine.

After disabling the workfow for 2mn, and restarting it again, it worked again fine. (I tried to stop/start immediately afterwards, and that hadn’t fixed it, only by waiting a few minutes did that solve it)

I’m not sure what went wrong, why, and what to provide to help with further understanding of the root issue.

What is the error message (if any)?

Error: No active execution found
    at ActiveExecutions.getExecution (/app/code/node_modules/n8n/src/ActiveExecutions.ts:255:10)
    at ActiveExecutions.getStatus (/app/code/node_modules/n8n/src/ActiveExecutions.ts:220:15)
    at /app/code/node_modules/n8n/src/WorkflowRunner.ts:336:49
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

Please share your workflow

Share the output returned by the last node

There is no output, the first node doesn’t even run.

Information on your n8n setup

• n8n version: 1.52.2
• Database (default: SQLite): Postgres
• n8n EXECUTIONS_PROCESS setting (default: own, main): Unsure
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker, via Cloudron App
• Operating system: Ubuntu 22

[Vadorequest]

I upgraded n8n to n8n 1.53.1 and after the auto server restart, the issue happened again.

I stopped the workflow again, waiting for all executions to fail, and started it again. It works again now.

But this is very confusing and doesn’t feel reliable.
This is the only workflow that seems to be affected, and the only one using a cron job to start.

[Jon]

Hey @Vadorequest,

This is a bit of an odd one, It looks like maybe the workflow failed to start properly. Can you share what env options you have set?

[Vadorequest]

Here is the config.

I’ve noticed the workflow failing from time to time since then, I’m not sure why.
Happened today around 7:15 during 1h15 and then seems to have somehow fixed itself. It’s running fine at the moment.

Using version n8n 1.53.2.

# https://docs.n8n.io/reference/environment-variables.html
export EXECUTIONS_DATA_SAVE_MANUAL_EXECUTIONS=true
export EXECUTIONS_DATA_SAVE_ON_ERROR=all
export EXECUTIONS_DATA_SAVE_ON_SUCCESS=all

export EXECUTIONS_DATA_PRUNE=true
export EXECUTIONS_DATA_MAX_AGE=365

export GENERIC_TIMEZONE='Europe/Paris'
export TZ='Europe/Paris'

# ------------- NODE MODULES ---------------------

# Allow node modules to be used in code node - https://docs.n8n.io/hosting/configuration/#use-built-in-and-external-modules-in-the-code-node
# Allows usage of all builtin modules
export NODE_FUNCTION_ALLOW_BUILTIN=*

# FYI This is a SPACE separated list
export EXTRA_NODE_MODULES="[email protected] [email protected] [email protected]"

# Allow usage of external npm modules
# Those modules are auto-installed by Cloudron upon app restart, see https://forum.cloudron.io/topic/11946/how-to-install-npm-packages-that-n8n-app-can-use/4?_=1719382777426
# FYI This is a COMMA separated list
export NODE_FUNCTION_ALLOW_EXTERNAL=cloudinary,node-fetch,form-data

# ------------- LOGGING ---------------------

# Set the logging level to 'debug'
export N8N_LOG_LEVEL=debug

# Set log output to both console and a log file
#export N8N_LOG_OUTPUT=console,file

# Set a save location for the log file
# FYI I don't know where to store them
#export N8N_LOG_FILE_LOCATION=/home/jim/n8n/logs/n8n.log

# Set a 50 MB maximum size for each log file
#export N8N_LOG_FILE_MAXSIZE=50

# Set 60 as the maximum number of log files to be kept
#export N8N_LOG_FILE_MAXCOUNT=60

# Make sure to end with a blank row, otherwise might cause bugs

# ------------- BINARY ---------------------

# n8n workflows should write/read files at /app/data/n8n-uploads

[Jon]

Hey @Vadorequest,

Looking at your env options it is likely to be this…

export GENERIC_TIMEZONE='Europe/Paris'
export TZ='Europe/Paris'

Can you change these to the below and let me know if it improves it?

export GENERIC_TIMEZONE=Europe/Paris
export TZ=Europe/Paris

[Vadorequest]

Odd, as it did select the correct timezone by default for new workflows, using those settings.

I’ve changed those, and I’ll keep an eye on it, thank you!