n8n errors / Schema
cannot drop column role of table "user" because other objects depend on it
Cause
A migration tries to drop the legacy 'role' column but Postgres blocks the DROP because a constraint or index still references it, usually from a schema that diverged during an earlier upgrade.
Fix
Downgrade to the last working version before retrying the upgrade. Identify dependents with SELECT conname FROM pg_constraint WHERE conrelid='public.user'::regclass, drop them with ALTER TABLE public.user DROP CONSTRAINT <name>, then restart n8n to retry. Watch the GitHub issue for an official patch.
Part of the Automation Error Index — n8n errors: browse all.
Hitting an automation error we have not covered?
AutomateLab builds and debugs n8n, Make, and agent workflows as fixed-scope projects. If something is broken in production, tell us what you are seeing.
Describe the problem