Workflow Artifacts v2

A Workflow includes both source and, when published, a compiled artifact.

Source and revision identity

Workflow YAML is the editable source. A save records a new source revision when the content has changed and returns the latest FileHash used for concurrency control.

Compilation

The Runtime validates, renders, and compiles the Workflow source into a .NET assembly. Errors that occur during the publish operation, are surfaced to the Console and appear in the Problems pane.

Running a Workflow under debug skips saving it and instead compiles it on the fly in the runtime. This path avoids touching storage and is much faster. It is only necessary to save a Workflow when meaningful progress has been made to its behavior.

Published artifact

Publish stores the compiled artifact and associates it with the Workflow, Environment branch, and source FileHash.

The Manage releases view considers an Environment current when its branch source hash matches the latest published artifact hash. A source revision can therefore exist without being the active published revision if compilation or publish failed.

Save, publish, and run

Clicking Save in the Console performs both a save and a publish to the test Environment. It is possible that the publish will fail due to a validation or compile error in which case, the Workflow YAML is saved but the published version will not be updated.

With Release Management enabled, later Environments receive a compiled artifact through promotion. Without Release Management, save/publish targets all Site Environments.

See also

See Compiled Execution, Workflow Validation, Revisions and Releases, and Release Management Pane.