---
lastModified: 2026-09-10
title: "Conflict — your changes were not saved"
description: "Workflow editing, validation, and conflicting saves. Exact Runner messages, recovery steps, and checks for the completed result."
---

Correct the named field, node, connection, JSON, schedule, or file before retrying. Connections must use compatible inputs/outputs and cannot create cycles. Use a valid workflow export for import.

For a save conflict, preserve any local edits you need before choosing Reload server version: that action replaces the local workflow and unsaved node changes. Reopen a node when its underlying workflow changed. If the draft changes during deployment review, close the review and open Deploy again. A restored draft that requests a reload is already restored; reload the canvas rather than restoring again.

A comparison/history load failure does not change the deployed workflow. Refresh a rollback conflict to see what another person deployed. Confirm the saved draft, restored canvas, or active version matches your intent before deploying or enabling a trigger. If uncertainty remains, provide the workflow and version identifiers to support.

**Messages covered:**

- `Add a short note describing what changed.`
- `The draft changed after this review started. Close this review and open Deploy again.`
- `Invalid JSON.`
- `That output cannot connect to this input. Choose compatible nodes that do not create a cycle.`
- `Couldn’t update custom inputs or outputs: {message}`
- `Enter a node name before saving.`
- `Payload must be a JSON object.`
- `Schedule configuration is invalid.`
- `Publish your store to use Live Test. Simulate still works.`
- `The workflow changed while you were editing. Your draft is preserved. Discard it and reopen this node to review the latest changes.`
- `Couldn’t finish saving before restoring. Please try again.`
- `The draft was restored, but the canvas needs to be reloaded.`
- `Couldn’t verify the current draft version. Please refresh and try again.`
- `Save failed`
- `Couldn’t compare this version with the active deployment.`
- `Couldn’t compare this saved draft with the current canvas.`
- `Couldn’t load this saved draft for comparison.`
- `Your saved drafts are still safe. Check your connection and try again.`
- `Couldn’t load draft history`
- `Check your connection and try again.`
- `Couldn’t load version history`
- `Couldn’t restore this draft. Please try again.`
- `Couldn’t prepare this restore.`
- `Someone else deployed while you were rolling back. Please refresh.`
- `Rollback failed`
- `This file is not a valid workflow export.`
- `Could not read this file.`
- `Conflict — your changes were not saved`
- `Reload server version`
- `This replaces your local workflow and any unsaved node changes with the latest server version.`
- `Reload server version?`
- `Resolve the save conflict before deploying.`
- `Node “{nodeId}” is missing required field “{fieldName}”`
- `Node “{nodeId}” has an invalid Marketing Email source or delivery policy`
- `Node “{nodeId}” has an invalid transactional email render source`
- `Enter a valid 5-field cron expression.`
- `Enter a valid IANA timezone, such as America/Los_Angeles.`
- `An agent changed this node`
- `The agent removed the node you’re editing. Reload the agent’s changes or discard them to keep your draft.`
- `Reload agent changes`
- `Discard agent changes`
- `Your staged connection now conflicts with the agent's changes. Adjust or remove the connection, then try again.`

For repeated failures, see [what to send Runner](/en/guides/help-and-reference/error-playbook-store-and-apps).