fix(n8n): resolve duplicate key constraint on tag_entity during workflow import #49

Merged

Ichitux merged 1 commits from fix/n8n-init-duplicate-key-constraint into main

2026-07-17 13:00:34 +00:00

Author	SHA1	Message	Date
Antoni Nuñez Romeu	b4b2bf5834	fix(n8n): resolve duplicate key constraint on tag_entity during workflow import Run Tests on Branches / Detect Changes (push) Successful in 12s Details Run Tests on Branches / Backend Tests (push) Has been skipped Details Run Tests on Branches / Frontend Tests (push) Has been skipped Details Run Tests on Branches / Frontend Mobile Tests (push) Has been skipped Details Run Tests on Branches / Parapharmacy API Tests (push) Has been skipped Details Run Tests on Branches / PIP Platform Tests (push) Has been skipped Details n8n import:workflow --separate imports each JSON file independently. All 4 workflows shared the same tags (parapharmacy, scraper), so the second import tried to INSERT duplicate tag names, hitting the unique index on tag_entity.name. - Remove tags field from all 4 workflow JSON files (cosmetic, re-add via UI) - Add cleanup-db.js to wipe workflow data before import - Add --overwrite flag to import command as safety net - Add cleanup-db.js volume mount to n8n-init container	2026-07-17 14:50:35 +02:00