I’m triggering an n8n workflow from an Airtable button using a webhook (production URL). The workflow executes successfully (I see it in the executions tab), but the downstream nodes don’t seem to run with the latest updates I made in the editor.
The Airtable record updates, but changes in nodes (like Set / HTTP / logic updates) are not reflected in the execution.
What could cause the workflow to run an older version instead of the updated one?
Share the output returned by the last node
I am trying to handle these nulls. but this is the output I get in the Executions tab (Not the Editor!), seems like not updated.
same Node in the Editor
Information on your n8n setup
- n8n version: 2.15.1 (Cloud)
- Database (default: SQLite): Managed by n8n Cloud
- n8n EXECUTIONS_PROCESS setting (default: own, main): Managed by n8n Cloud (default)
- Running n8n via (Docker, npm, n8n cloud, desktop app): n8n Cloud
- Operating system: macOS
welcome to the n8n community @slash_gamer
You have unsaved changes in the editor.
check if there’s an orange/yellow dot next to the workflow name, that means you have pending unsaved changes.
I usually, after making any changes to your nodes, just hit Save (top right of the editor) before triggering the webhook again.
make sure you’re using the Production webhook URL in your Airtable button, not the Test URL. The test URL only works when you manually click “Execute step” inside the editor. But since executions are already showing up in your tab, that part seems fine, so saving the workflow should do the trick!
Hope that helps!
Hi @slash_gamer, welcome! Just publish your flow each time you have made a new change in the workflow.
hi Tami,
You mean press on publish again, right? as I dont see any “save” button
top right that Yellow flashing says Publish.
Yes — in the current editor UI, Publish is effectively the new save/apply action for the live workflow. If you’ve made changes and don’t see a separate Save button, clicking Publish updates the published version that triggers and webhooks use. If you only changed the draft and didn’t publish again, the live webhook may still be using the older version.
Let me know if it works @slash_gamer
