Create and test a workflow

A workflow describes the steps an AI workload follows. Use the visual editor to prepare those steps, save a version, and test a release before requesting review.

Before you start

Select the correct workspace. You need asset authoring access, an appropriate owner, and any approved models, prompts, or connections your workflow needs. Testing and release actions require additional permissions.

Agree on the workflow’s purpose, inputs, expected result, and external effects. Use approved test data and connections. A non-production test can still call a service or consume model resources.

Choose a starting point

Open Build → Assets and select New Workflow. Choose the method that fits your task:

Starting point	How to use it
With Assistant	Describe the task, answer any clarification question, and review the proposed workflow. Select Add to canvas when the proposal is suitable. Explicitly name existing assets needed as context; generation does not automatically inspect your workspace’s asset inventory.
Blank canvas	Start an empty workflow and open it in the editor.
Start from template	Browse the available templates and inspect the selected starter before using it.
Import	Supply your existing workflow definition and select Load into editor. Resolve any import errors before continuing.
Duplicate	Select an existing workflow and version, then select Duplicate into editor. Review references rather than assuming that all dependencies suit the new purpose.

AI-generated content is a draft. Inspect its logic and asset references before saving or running it.

Read the readiness panel

Workflow readiness panel showing Orientation, Identity and Source still required, with Open in editor disabled

Workflow readiness panel observed in the intended Orqestra environment on 18 October 2026. Read it from top to bottom: Orientation is the starting point, Identity is the slug and owner, and Source is the chosen starting content. The editor becomes available when the required setup is complete. Entering the editor is separate from saving the workflow.

Apply a catalog template to a workload

The Build → Catalog → Templates page provides a separate shortcut: select a template, inspect its preview and instructions, choose Workload and Environment, then select Use Template. This creates a workflow and a draft release for that workload. Check the confirmation and inspect the new draft under Assure → Releases. It does not activate the workload.

Edit and save

In Canvas, add the steps you need, connect their paths, and select each step to configure its properties. Use YAML if you prefer to edit the definition as text.
Select the approved model, prompt, or connection required by each relevant step. If Orqestra asks for a release context, choose the intended workload and non-production environment.
Open Review and resolve the issues shown. Select Validate to inspect the current validation result.
Select Save. If prompted, complete Slug and Owner, then select Continue.
Check the saved workflow and its version. When editing an existing workflow, saving creates a new version; it does not rewrite a previously released version.

Validation checks the definition within its scope. It does not prove that the workflow produces the right business result or that an external service will respond successfully.

Test the saved configuration

Save the changes you intend to test.
Use Set up release… if there is no release context. Confirm the workload, environment, and required release details.
Check the readiness indicator and resolve blocking requirements.
Select Test run and inspect the run details and outcome.

Test run uses the last saved release version, including its bound assets. Unsaved canvas changes are excluded. Test runs require a non-production release and a synchronized workflow binding. Use testing and evaluation to assess cases and quality beyond one execution.

When ready, select Request release if available, or prepare the release for review. Requesting review does not activate it.

If something fails

Problem	What to do
Assistant generation is unavailable	Use a manual starting point, or ask the operator to check generation availability.
Validation reports an issue	Review the named step, required field, or reference. Correct it and validate again.
Release out of sync appears after saving	The workflow version saved, but the release still references an earlier version. Use Retry, Start a new draft, or Reset context only as offered by the message, then confirm the binding before running.
Test run is disabled	Read its explanation. Check release context, non-production environment, synchronization, and whether a run is already in progress.
Template creation or saving has an uncertain result	Inspect existing workflows and releases before repeating creation. Ask the owner if you cannot confirm the result.

Test and evaluate changes, operate a release, or manage assets and versions.