Editing, Apply and Save
Distinguish an Editor draft, Core's active state and the saved project.
AlphaA draft is a change waiting in the Editor. Apply changes Core's active configuration; Save writes the applied project to disk.
Three states
| State | Where it lives | What uses it |
|---|---|---|
| Draft | Editor | Forms and pending edits |
| Applied | Core | Later accepted events and controlled tests |
| Saved | Project file | A later project open or restart |
In Automation and Macros, use File → Save (Ctrl+S) to validate and apply pending sequence edits, then write the project. These workspaces do not have a separate Apply button. Resolve validation failures rather than assuming a failed save succeeded.
Plugin entity and service-settings forms expose Apply and Discard or Cancel controls. Apply commits that form's changes to Core; saving the project is a separate operation. Check the form's scope before expecting local service settings to be included in a project file.
Autosave belongs to Core and continues when the Editor closes. It saves applied state, not a draft retained only in an Editor.
Test the intended definition
The automation Test command uses the applied definition and the chosen test data. It does not apply your draft. In Automation, save the edited sequence before testing it. In a form with an Apply button, apply its changes first.
An active run retains the definition captured for that run. Applying an edit changes later accepted runs; it does not replace steps already captured by an active run.
Conflicts and uncertain results
Another client may change a resource before your Apply. A conflict preserves your draft for review. Reload and compare before applying a deliberate new edit.
If the connection is lost during a command, its outcome can be unknown. Wait for recovery or inspect the resulting Core state. Repeating an action with a new command can duplicate external effects.
See Changes not appearing, Projects and Core, Editor and Tray.