← Back to Notes
n8nJuly 2, 2026

Why You Need to Re-Publish n8n Workflows After Every Edit

Use this as a reminder any time a fix doesn't seem to take effect even though the node clearly shows the updated configuration.

Steps

  1. Make the fix inside a node, save the node.
  2. Save the workflow itself if prompted.
  3. Click Publish (or toggle Active off and back on, depending on the version) again, even if the workflow was already published before the edit.
  4. Only then re-trigger a real test.

Gotcha

On instances using a publish/versioning model, editing and saving a node updates a draft, but real incoming triggers (a webhook, a scheduled run) keep executing whatever was last published. This can look exactly like the fix "didn't work," when actually the fix is correct and simply hasn't gone live yet. If a bug seems to persist identically after a fix, checking whether the workflow was republished is a fast, easy thing to rule out before spending more time debugging the logic itself.

Quick reference

Fix → Save node → Save workflow → Publish → then test.