Worker failed to find data for execution

Describe the problem/error/question

I am currently facing an issue regarding execution missing data. I currently updated to latest published version 1.103.2 (Which on n8n official repository is still a pre-release curiously).

What is the error message (if any)?

This is the error occuring to multiple executions.

Worker errored while running execution 37137 (job 470)
Worker failed to find data for execution 37137 (job 470) (execution 37137)
Error: Worker failed to find data for execution 37137 (job 470)
    at JobProcessor.processJob (/usr/local/lib/node_modules/n8n/src/scaling/job-processor.ts:59:10)
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
    at Queue.<anonymous> (/usr/local/lib/node_modules/n8n/src/scaling/scaling.service.ts:103:5)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.103.2
  • Database: Postgres
  • n8n EXECUTIONS_PROCESS setting: main
  • Running n8n via: Docker
  • Operating system: Ubuntu 20.04

This error appears when attempting to process a queued job, but failing to load data from the database or store. GitHub Issue #12535 suggests that the error arises when the execution was deleted or never saved correctly, and the worker can’t find the corresponding data.

Other threads also report that if an execution is canceled or orphaned in Redis, it could block the queue and generate the same error.

I recommend checking:

  • Data integrity in Redis/Postgres.
  • Centralized queue configuration.
  • Enable DEBUG logs.

Issue OP is myself. The error occurs even before the node execution, i.e., it does not even start manually. Example: Schedule and Webhook Nodes triggering fail without passing data through.

Additionally, which actions should be performed for below suggestions?

  • Data integrity in Redis/Postgres.
  • Centralized queue configuration.
  • Enable DEBUG logs.

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