[SOLVED] Workflow could not be activated (after domain switch)

Questions
1

I saw this question a few times but most of them are not allowing new comments.

Basically, for me, this happened when I switched my domain, but I saw people that this happened to when switching from different environments.

Basically, for me, the solution was:

  1. Duplicate any webhook trigger node in the damaged workflow
  2. Disable the old webhook trigger nodes
  3. Hook up the new webhook trigger nodes to the same place
  4. Try activating the workflow (should work now!)
  5. Delete old webhook trigger nodes

This seemed to work for all my damaged pipelines.

Hope this helped!

  • n8n version: 1.69.2
  • Database (default: SQLite): postgres:16
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default?
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Unraid (linux)
1 Like
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Thanks for sharing.

1 Like
4

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