My n8n workflow is not running as it was in older versions

Anonymous
HOBBY

15 days ago

I have a workflow that was perfectly working on n8n 1.94.1, but today all the executions were getting in queue mode, so I decided to update everything to the latest version.

But when I ctrl+c ctrl+v the workflows, the new version executes, but it stops on a specific node (Code). I'm seeing some people talking about the postgres, the worker and etc. I have to solve this problem, the workflow is no running.

I'm trying to change postgres version, but it's not working.

Attachments

image.png
Screenshot%...
$10 Bounty

2 Replies

Railway
BOT

15 days ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!

aegiesauth
PRO

15 days ago

1. n8n Queue Mode and Worker Setup

  • Queue mode was introduced and improved in recent n8n versions, which now requires a properly configured Redis instance and often a multi-worker setup.

  • If you run n8n in queue mode, the main process only schedules jobs via the REST API or UI, and dedicated n8n worker processes execute jobs. If workers are not started or not connected, jobs remain queued indefinitely.

  • Check:

    • Are dedicated n8n worker processes running?

    • Is your Redis instance accessible and healthy?

  • Fix:

    • Start at least one worker with:

      text

      n8n worker

    • Ensure the worker can connect to the same Postgres and Redis instances as your main n8n process.

2. Postgres Database Migrations

  • Major upgrades might introduce SQL migrations or changes in how executions are stored and handled.

  • Check:

    • Run database migrations, if instructed by release notes.

    • Check n8n logs for migration errors.

3. Code Node Changes

  • The behavior of the Code node (JavaScript/TypeScript execution) may change between releases, especially regarding sandboxing and permissions.

  • Check:

    • Review error logs for the node — sometimes new syntax or package restrictions get introduced.

    • Make sure any custom npm modules you rely on are still accessible.

    • n8n may have tightened security on code execution. Refer to latest n8n docs: Code Node.

4. Logs and Error Messages

  • Examine the full output and error logs from Docker, CLI, or your hosting environment for clues.

  • Node-specific logs will often tell you if it's a database, queue, or execution environment issue.

5. Configuration Changes

  • Environment variables such as N8N_EXECUTIONS_PROCESS setting, queue options (REDIS_*, QUEUE_MODE), and database credentials may need to be reviewed after an upgrade.

  • Ensure consistency across all processes (main, webhooks, worker).

Immediate Steps to Unblock Execution

  1. Launch at least one n8n worker:

    n8n worker

  2. Ensure Redis is running and reachable.

  3. Confirm your Postgres database is connected and no pending migrations exist.

  4. If jobs remain stuck, restart all n8n services (main, worker, webhooks).

  5. If the Code node specifically fails, review recent breaking changes in the n8n upgrade changelog for that node.

Additional References