Changes not appearing

If a test still uses an old value, first inspect Apply and Save. A visible edit may still be an Editor draft.

Check in order

1. Confirm the intended Core project is open.
2. Resolve validation errors. For Automation or Macros, use File → Save (Ctrl+S); for a form with an Apply button, apply that form's changes.
3. Select the intended Test Data preset and run Test again.
4. Select the new run in Runs; an older run retains its original captured values.
5. Save after the applied definition behaves as expected.

Autosave does not make an unapplied draft active. An already running automation keeps its captured definition even after a later Apply.

Conflict

Another client or operation changed the resource. Keep your draft, refresh the applied state and compare the conflicting fields before submitting a deliberate new edit.

Unknown command outcome

If the connection dropped during Apply, Save or a runtime command, wait for command recovery and inspect Core's resulting state. A missing response does not prove the operation failed. Do not repeatedly trigger an external action to test whether it was accepted.