Error importing Workflows from CLI

[jsa4000]

Bug Description

Hi,

From n8n version 1.117.X I am getting some exceptions when importing workflows from already exported files. The workflows seems to be imported in n8n properly, but it throws exceptions.

Could not remove webhooks of workflow "srOnR8PAY3u4RSwb" because of error: "Could not find workflow"

To Reproduce

1. Go to https://github.com/n8n-io/self-hosted-ai-starter-kit and clone it.
2. Start docker compose up
3. When the n8n-importservice it's initializing, it will throw errors when importing workflows

Expected behavior

It should not throw any exception when importing.

Debug Info

This is the exception throw when importing.

n8n-import  | Importing 1 workflows...
n8n-import  | Could not find workflow
n8n-import  | Error: Could not find workflow
n8n-import  |     at ActiveWorkflowManager.clearWebhooks (/usr/local/lib/node_modules/n8n/src/active-workflow-manager.ts:254:10)
n8n-import  |     at processTicksAndRejections (node:internal/process/task_queues:105:5)
n8n-import  |     at ActiveWorkflowManager.remove (/usr/local/lib/node_modules/n8n/src/active-workflow-manager.ts:874:4)
n8n-import  |     at ImportService.importWorkflows (/usr/local/lib/node_modules/n8n/src/services/import.service.ts:78:5)
n8n-import  |     at ImportWorkflowsCommand.run (/usr/local/lib/node_modules/n8n/src/commands/import/workflow.ts:104:3)
n8n-import  |     at CommandRegistry.execute (/usr/local/lib/node_modules/n8n/src/command-registry.ts:67:4)
n8n-import  |     at /usr/local/lib/node_modules/n8n/bin/n8n:63:2
n8n-import  | 
n8n-import  | Could not remove webhooks of workflow "srOnR8PAY3u4RSwb" because of error: "Could not find workflow"
n8n-import  | Successfully imported 1 workflow.

Operating System

MacOS Tahoe

n8n Version

1.117.1

Node.js Version

N/A (running docker)

Database

PostgreSQL

Execution mode

main (default)

Hosting

self hosted

[jsa4000]

Hi, any update on this issue?

[newtonetwork]

was also able to replicate when trying a fresh install.

[BanovMiroslav]

I am also getting this error. My initial script that starts my n8n for the first time fails. The script creates some initial credentials and workflows and a user. I imagine I am not the only one doing something like that. I had to ignore the error from n8n import:workflow to fix it, but that's not ideal.

[AshDevFr]

I am also having the same issue on n8n:1.123.4

The error is slightly different but same thing I believe:

Could not find workflow
Error: Could not find workflow
    at ActiveWorkflowManager.clearWebhooks (/usr/local/lib/node_modules/n8n/src/active-workflow-manager.ts:257:10)
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
    at ActiveWorkflowManager.remove (/usr/local/lib/node_modules/n8n/src/active-workflow-manager.ts:907:4)
    at ImportService.importWorkflows (/usr/local/lib/node_modules/n8n/src/services/import.service.ts:84:5)
    at ImportWorkflowsCommand.run (/usr/local/lib/node_modules/n8n/src/commands/import/workflow.ts:104:3)
    at CommandRegistry.execute (/usr/local/lib/node_modules/n8n/src/command-registry.ts:67:4)
    at /usr/local/lib/node_modules/n8n/bin/n8n:63:2

Could not remove webhooks of workflow "zjoHiAr4MvT0WXFG" because of error: "Could not find workflow"
An error occurred while importing workflows. See log messages for details.
insert or update on table "workflow_publish_history" violates foreign key constraint "FK_c01316f8c2d7101ec4fa9809267"
insert or update on table "workflow_publish_history" violates foreign key constraint "FK_c01316f8c2d7101ec4fa9809267"

[GauthierPLM]

Hello,
We are encountering the same issue with version 1.123.5, deployed via Docker.
We use the following start script:

#!/bin/sh

# Create the n8n configuration file with the encryption key from doppler
echo "Creating n8n configuration file..."
echo "{ \"encryptionKey\": \"$N8N_ENCRYPTION_KEY\" }" > /home/node/.n8n/config

if [ "$IS_MAIN_NODE" = "true" ]; then
  echo "Starting n8n in main node mode..."

  # Import all workflows and credentials if the N8N_AUTO_UPDATE_WORKFLOWS environment variable is set to true on doppler
  if [ "$N8N_AUTO_UPDATE_WORKFLOWS" = "true" ]; then
    echo "Auto-updating workflows enabled, importing all workflows..."
    sh /internal-import-all-n8n.sh
  fi

  # Active Airtable Triggers n8n workflow if the N8N_ACTIVE_AIRTABLE_TRIGGERS environment variable is set to true on doppler
  if [ "$N8N_ACTIVE_AIRTABLE_TRIGGERS" = "true" ]; then
    echo "Activating Airtable Triggers workflow..."
    n8n update:workflow --id=IwAVtYXRDSKaiFGN --active=true
  fi

  # Activate workflows that should only run in prod environment
  if [ "$DOPPLER_ENVIRONMENT" = "prod" ]; then
    echo "Activating workflows that should only run in prod environment..."
    # Cloudflare Images - Sync company logos
    n8n update:workflow --id=DGqLsQVsaNNkRtj5 --active=true
    # Cloudflare Images - Sync company logos
    n8n update:workflow --id=E67kdrlzOSMfSPMz --active=true
    # Cloudflare Images - Sync foundational reports thumbnails
    n8n update:workflow --id=EUhFSxGCwR39TJih --active=true
    # Cloudflare Images - Clean orphan images
    n8n update:workflow --id=1SpHP1EfmWfegWXT --active=true
  fi

  # Activate "Refresh Search Index - Scheduled refresh" workflow
  echo "Activating Refresh Search Index - Scheduled refresh workflow..."
  n8n update:workflow --id=QkaVq3C800hq2ueM --active=true

fi

# Execute doppler run and then pass control to the original entrypoint script
echo "Starting n8n with Doppler configuration..."
exec /docker-entrypoint.sh "$@"

This is the logs we have:

 2025-Dec-12 13:07:03.759307 Importing 55 workflows...
2025-Dec-12 13:07:03.825382 Could not find workflow
2025-Dec-12 13:07:03.825422 Error: Could not find workflow
2025-Dec-12 13:07:03.825429 at ActiveWorkflowManager.clearWebhooks (/usr/local/lib/node_modules/n8n/src/active-workflow-manager.ts:257:10)
2025-Dec-12 13:07:03.825434 at processTicksAndRejections (node:internal/process/task_queues:105:5)
2025-Dec-12 13:07:03.825438 at ActiveWorkflowManager.remove (/usr/local/lib/node_modules/n8n/src/active-workflow-manager.ts:907:4)
2025-Dec-12 13:07:03.825442 at ImportService.importWorkflows (/usr/local/lib/node_modules/n8n/src/services/import.service.ts:84:5)
2025-Dec-12 13:07:03.825446 at ImportWorkflowsCommand.run (/usr/local/lib/node_modules/n8n/src/commands/import/workflow.ts:104:3)
2025-Dec-12 13:07:03.825450 at CommandRegistry.execute (/usr/local/lib/node_modules/n8n/src/command-registry.ts:67:4)
2025-Dec-12 13:07:03.825454 at /usr/local/lib/node_modules/n8n/bin/n8n:63:2
2025-Dec-12 13:07:03.825458
2025-Dec-12 13:07:03.826208 Could not remove webhooks of workflow "1GSDowxngq3AIril" because of error: "Could not find workflow" 

When we manually try to activate the workflow, we get the following error:

2025-Dec-12 13:07:09.948322 Activating Airtable Triggers workflow...
2025-Dec-12 13:07:12.359146 Permissions 0644 for n8n settings file /home/node/.n8n/config are too wide. This is ignored for now, but in the future n8n will attempt to change the permissions automatically. To automatically enforce correct permissions now set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true (recommended), or turn this check off set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=false.
2025-Dec-12 13:07:14.025802 Activating workflow with ID: IwAVtYXRDSKaiFGN
2025-Dec-12 13:07:14.037443 Error updating database. See log messages for details.
2025-Dec-12 13:07:14.037639
2025-Dec-12 13:07:14.037650 GOT ERROR
2025-Dec-12 13:07:14.038227 ====================================
2025-Dec-12 13:07:14.038738 insert or update on table "workflow_entity" violates foreign key constraint "FK_08d6c67b7f722b0039d9d5ed620"
2025-Dec-12 13:07:14.097590 QueryFailedError: insert or update on table "workflow_entity" violates foreign key constraint "FK_08d6c67b7f722b0039d9d5ed620"
2025-Dec-12 13:07:14.097641 at PostgresQueryRunner.query (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/@n8n+typeorm@0.3.20-15_@sentry+node@9.42.1_mysql2@3.15.0_pg@8.12.0_sqlite3@5.1.7/node_modules/src/driver/postgres/PostgresQueryRunner.ts:331:19)
2025-Dec-12 13:07:14.097645 at processTicksAndRejections (node:internal/process/task_queues:105:5)
2025-Dec-12 13:07:14.097648 at UpdateQueryBuilder.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/@n8n+typeorm@0.3.20-15_@sentry+node@9.42.1_mysql2@3.15.0_pg@8.12.0_sqlite3@5.1.7/node_modules/src/query-builder/UpdateQueryBuilder.ts:130:33)
2025-Dec-12 13:07:14.097651 at WorkflowRepository.updateActiveState (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/@n8n+db@file+packages+@n8n+db_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1._ab22bba05a964211b9fe14bf4b841570/node_modules/@n8n/db/src/repositories/workflow.repository.ts:828:11)
2025-Dec-12 13:07:14.097654 at UpdateWorkflowCommand.run (/usr/local/lib/node_modules/n8n/src/commands/update/workflow.ts:51:4)
2025-Dec-12 13:07:14.097656 at CommandRegistry.execute (/usr/local/lib/node_modules/n8n/src/command-registry.ts:67:4)
2025-Dec-12 13:07:14.097659 at /usr/local/lib/node_modules/n8n/bin/n8n:63:2
2025-Dec-12 13:07:14.097765 insert or update on table "workflow_entity" violates foreign key constraint "FK_08d6c67b7f722b0039d9d5ed620" 

[TomTom101]

+1 on 2.0.2 and 1.123.5
Works (for me) on 1.122.5
I cannot import workflows developed in another instance of the same version into a fresh database.

[TomTom101]

I believe the issue was introduced with adding the relations constraint in #21202:

n8n/packages/cli/src/active-workflow-manager.ts

Lines 249 to 252 in ac91020

	const workflowData = await this.workflowRepository.findOne({
	where: { id: workflowId },
	relations: { activeVersion: true },
	});

On newly imported workflows this relation is maybe non existant, at least activeVersion is not true?
It's the only change between 1.122 and 1.123 that can imagine to be the cause. However, I am not really familiar with the inner workings of n8n …

[ECOPLANCOM]

Any news here?

[daveperdue]

Looks like this has also carried over to 2.0.2.

[RossElder1983]

I believe the issue was introduced with adding the relations constraint in #21202:

n8n/packages/cli/src/active-workflow-manager.ts

Lines 249 to 252 in ac91020

const workflowData = await this.workflowRepository.findOne({
where: { id: workflowId },
relations: { activeVersion: true },
});
On newly imported workflows this relation is maybe non existant, at least activeVersion is not true? It's the only change between 1.122 and 1.123 that can imagine to be the cause. However, I am not really familiar with the inner workings of n8n …

Off the back of this and the fact i was having the same issue i pulled the 122.5 image and my import of workflows ran first go so id say you are on the money here!

[xmasterg]

Experieincing this error right now...

[UPDATE]
STATUS = Got it to import to the new v2.0.2. without downgrading the original docker.
NOTE = Also moved from sqlite (default) to postgres and redis for queueing.

Community nodes could not be installed via CLI (not sure why). Had to the workflow, click on the node and then from the node click install and all good.

Here are my steps in short (issues included):

`1.	Made a backup from the old n8n instance:
•	Exported workflows (separate JSON files)
•	Exported credentials (separate JSON files)
•	Exported full entities (n8n export:entities)
•	Saved encryption key (N8N_ENCRYPTION_KEY)
2.	Set up a fresh n8n v2.0.2 instance with Postgres (Docker).
3.	Verified the new instance uses the same encryption key as the old one.
4.	Imported credentials first:
•	Used n8n import:credentials --separate
•	This worked without issues.
5.	Tried importing workflows via CLI:
•	Workflows were imported
•	CLI printed webhook-related errors (Could not find workflow)
•	Workflows still appeared in UI (known bug, ignored).
6.	Tried importing entities from old backup:
•	Got migration timestamp mismatch
•	Import refused to continue.
7.	Re-exported entities using n8n v2.0.2 (same version as target):
•	This fixed migration mismatch.
8.	Tried importing entities again:
•	Import failed with:
             "duplicate key value violates unique constraint "pk_workflows_tags" "
9.	Found that entities.zip contains two workflow tag mapping files:
•	workflows_tags.jsonl
•	workflowtagmapping.jsonl
10.	Removed one of the mapping files:
•	Deleted workflowtagmapping.jsonl
•	Repacked entities.zip
11.	Imported entities again:
•	Import completed successfully.
12.	Started n8n:
•	Workflows loaded
•	Some workflows failed to activate.
13.	Activation errors showed:
•	Unrecognized node type: n8n-nodes-scrapingbee
•	Unrecognized node type: @apify/n8n-nodes-apify
14.	Installed missing community nodes via n8n UI.
15.	Restarted n8n:
•	All workflows activated successfully
•	System fully restored.`

[soueldi]

Same on n8n v2.1.0

n8n import:workflow --separate --input=/backup/temp

Result :

• repeated: Could not remove webhooks of workflow "...": Could not find workflow
• then import fails with Postgres FK:
  insert or update on table "workflow_publish_history" violates foreign key constraint "FK_c01316f8c2d7101ec4fa9809267" FK definition: FOREIGN KEY ("workflowId") REFERENCES n8n.workflow_entity(id) ON DELETE CASCADE

[ARHAEEM]

Today in version V2.1.0, the problem returned after import workflows. just used 30 minutes of Gemini analyzing it, here’s the problem and quick fix script I got from him that fixed the problem.

Fix n8n Migration Error Plan

Goal

Resolve the FK_08d6c67b7f722b0039d9d5ed620 violation preventing n8n startup, and to handle the new activeVersionId schema correctly.

Problem Analysis

The migration ActivateExecuteWorkflowTriggerWorkflows1763048000000 generates a new version history for workflows with certain triggers and sets activeVersionId. The error occurs because the UPDATE workflow_entity fails FK check against workflow_history. This implies the preceding INSERT INTO workflow_history failed or was not visible. Potential causes:

1. Data inconsistency in workflow_entity (orphaned workflows from our sync?).
2. Transaction isolation issues (though unlikely to cause permanent failure in migration loop).
3. Missing activeVersionId handling in our code creating inconsistent state that the migration doesn't expect.

Proposed Changes

1. Database Fix Script (Immediate Relief)

Create a SQL script fix_n8n_migration.sql to:

• Identify workflows causing issues.
• Manually insert missing history or cleanup bad workflows to allow migration to pass.
• Hypothesis: Some workflows might exist without ANY history, or the migration logic is flawed for certain workflow states.

/*
 * n8n Migration Persistence Fix Script
 * -------------------------------------
 * This script resolves Foreign Key violations related to "FK_08d6c67b7f722b0039d9d5ed620"
 * which prevents n8n from starting during the "ActivateExecuteWorkflowTriggerWorkflows" migration.
 *
 * It performs two safe operations:
 * 1. NULLs out any activeVersionId that points to a non-existent history record.
 * 2. Creates missing history records for current workflows to ensure consistency.
 *
 * HOW TO RUN:
 * Execute this SQL against your n8n PostgreSQL database.
 * You can use a tool like pgAdmin, DBeaver, or psql.
 * Example: psql -d n8n_db -f scripts/cleanup_script.sql
 */

-- OPTIONAL: Wrap in transaction to ensure safety
BEGIN;

RAISE NOTICE 'Starting n8n database cleanup...';

-- 1. Fix Invalid Active Versions
-- If a workflow has an activeVersionId that doesn't exist in history, the FK constraint fails.
-- We fix this by resetting it to NULL (n8n will treat it as having no specific active version, which is safe).
UPDATE "workflow_entity"
SET "activeVersionId" = NULL
WHERE "activeVersionId" IS NOT NULL
  AND "activeVersionId" NOT IN (SELECT "versionId" FROM "workflow_history");

RAISE NOTICE 'Fixed invalid activeVersionId references.';

-- 2. Backfill Missing History
-- Ensure every workflow's current "versionId" exists in "workflow_history".
-- This prevents issues if n8n tries to set the current version as active.
INSERT INTO "workflow_history" (
    "versionId", 
    "workflowId", 
    "nodes", 
    "connections", 
    "createdAt", 
    "updatedAt", 
    "authors", 
    "name"
)
SELECT 
    w."versionId", 
    w."id", 
    w."nodes", 
    w."connections", 
    NOW(), 
    NOW(), 
    'cleanup-script', 
    w."name"
FROM "workflow_entity" w
WHERE w."versionId" NOT IN (SELECT "versionId" FROM "workflow_history")
ON CONFLICT ("versionId") DO NOTHING;

RAISE NOTICE 'Backfilled missing workflow history records.';

-- 3. Cleanup Orphaned History (Optional, good for hygiene)
-- DELETE FROM "workflow_history"
-- WHERE "workflowId" NOT IN (SELECT "id" FROM "workflow_entity");

RAISE NOTICE 'Cleanup completed successfully. You can now restart n8n.';
COMMIT;