Erro Missing process handler for job type __default__. Aborting

Describe the problem/error/question

Recently, several workflows started to give the error in the attached print. About 50% of the executions, in different workflows, apparently in an arbitrary way. Observing Redis, there was an accumulation of memory. A large number of executions with “new” status were also observed, at least 3 months old. These executions with this error cannot be reprocessed, generating another error “The execution was aborted before starting, so it cannot be retried”

I see in database the execution stay with status “new”, look at the log this executions aparentally has blocked like log ([infoe | eBlocked GET /workflow/lQV3QEtFb8BtjR5v/executions/25975340 for "Slackbot-LinkExpanding 1.0 (+https://api.slack.com/robots)"e “{ file: ‘AbstractServer.js’ }”)

What is the error message (if any)?

Problem with execution 25758245: Missing process handler for job type default. Aborting.e "{ file: ‘WorkflowRunner.js’ }

ENV configs

WEBHOOK_URL: “https://n8n.xpto.io/
N8N_METRICS: “true”
N8N_METRICS_INCLUDE_CACHE_METRICS: “true”
N8N_METRICS_INCLUDE_MESSAGE_EVENT_BUS_METRICS: “true”
N8N_METRICS_INCLUDE_WORKFLOW_ID_LABEL: “true”
N8N_METRICS_INCLUDE_API_ENDPOINTS: “true”
N8N_METRICS_INCLUDE_API_STATUS_CODE_LABEL: “true”
N8N_EDITOR_BASE_URL: “https://n8n.xpto.io
N8N_HOST: n8n.xpto.io
N8N_SMTP_SSL: “true”
N8N_LOG_LEVEL: debug
QUEUE_BULL_REDIS_HOST: redis-service
QUEUE_HEALTH_CHECK_ACTIVE: “true”
QUEUE_WORKER_LOCK_DURATION: “30000”
QUEUE_WORKER_STALLED_INTERVAL: “30000”
QUEUE_WORKER_MAX_STALLED_COUNT: “2”
EXECUTIONS_MODE: queue
EXECUTIONS_DATA_PRUNE: “true”
EXECUTIONS_DATA_PRUNE_MAX_COUNT: “10000000”

Share the output returned by the last node

Job don`t start

Information on your n8n setup

  • n8n version: 1.55.3
  • Database (default: SQLite): PostgreSQL
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): kubernetes
  • Operating system: linux
1 Like

Got the same error here I don’t know why. Didn’t change my workflow.

2 Likes

I have the same error too. Anything from the n8n team? This is ruining our operations.

Up on this, still the same problem on a lot of different workflows!

We solved this problem by increasing RAM and decreasing the size of workflows

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