Revisions, drafts, and copying
Every workflow has a stable parent, a mutable editor draft, and immutable saved revisions.
Drafts
Section titled “Drafts”The browser autosaves editor state so incomplete work can survive navigation. A draft is not executable and may be temporarily invalid.
Revisions
Section titled “Revisions”Selecting Save changes validates the complete definition and publishes a new immutable revision. Existing runs remain pinned to the revision from which they were created.
This means:
- editing a workflow never changes an already published run;
- registry changes do not rewrite saved revisions; and
- teams can audit which definition produced a run.
Concurrent edits
Section titled “Concurrent edits”txcast uses revision and draft versions to prevent stale saves. If another tab, person, or agent saved after your view loaded, the stale write receives a conflict.
Refresh and compare before retrying. Agents replace only a complete strict draft and cannot silently overwrite an incomplete human draft.
Copy instead of edit
Section titled “Copy instead of edit”Only the author edits a workflow. Copy or fork a workflow to:
- adapt a shared template;
- test a new account or chain;
- keep a production version stable; or
- create a variation with different dependencies.
After copying, revalidate all targets, accounts, variables, and ABI functions. A copy preserves structure, not an assurance that current chain state is safe.