Skip to content

Start here

Saving, drafts, and keyboard shortcuts

Understand autosave, explicit saves, unsaved changes, and editor shortcuts.

The editor distinguishes a local draft from a successfully saved workflow. Watch its save indicator, especially after a connection problem or an incomplete job.

Save deliberately

Save persists a valid definition. Save & Run persists and starts processing. Autosave can save eligible edits in the background, but pauses when the draft is incomplete—for example, while a newly added job has no handler. Finish configuring the job to resume autosave.

The status can show Saving, Saved, Unsaved, or an autosave-paused message. An Unsaved indicator means you should resolve the problem before assuming the server has your latest edits. A restored local draft can help recover work after navigation or reload, but it is not equivalent to a confirmed server save.

When leaving with unsaved changes, read the navigation guard and choose whether to stay, save, or discard as offered. Do not assume closing a browser tab successfully uploads a draft.

Editor shortcuts

ShortcutAction
Command/Ctrl+SSave the workflow.
Command/Ctrl+EnterSave and run, outside multiline editing contexts.
Command/Ctrl+ZUndo the last canvas edit.
Command/Ctrl+DDuplicate the selected job.
Command/Ctrl+ASelect canvas nodes when canvas focus permits.
DeleteRemove the selected job or edge.
?Open the canvas shortcut reference.

Tab and Shift+Tab move focus. Enter or Space selects a node; Escape deselects; arrow keys move the selected node. Text inputs retain their normal editing behavior where appropriate.

Resolve conflicting edits

A workflow can change while you are editing it. If a save reports a revision conflict, refresh the current definition, compare it with your intended change, and reapply deliberately. Repeatedly retrying an old save does not merge competing edits.

Undo affects draft changes. It cannot retract a completed model call or undo an external write from Save & Run. See versions and reliability.