Orkestia
Blog
Cockpit app

Workflows builder

Build, check, save, run and schedule a workflow in Orkestia Cockpit — the steps and diagram views, blocks, the Test run, versions and drafts, past runs and the assistant panel

Workflows (Build group) is the editor for the organization's workflows. Describe what should happen step by step; the app compiles it into the platform's composition format, checks it with the platform, saves it as a version, runs it and follows the run on the steps. For what a workflow is, read Workflows and Virtual workflows; this page is about the editor.

The list is on the left, the open workflow on the right. Nothing you build is run for real until you press Run….

The list

PartBehavior
CountN workflows, or N of M workflows while a filter is on
Search name, description, tag or idNarrows as you type. Esc clears
Filter buttonOpens Filter and sort (below). A badge counts active filters; each shows as a removable pill, and Clear removes them all
New Workflow (+)Starts an unsaved workflow. It appears under Not saved yet until you save
ReloadReads the list again. The app also reloads when the window regains focus, so saves made on the web or by the assistant show up
RowName, then Live · vN, Draft vN · live vM or Not saved yet, step count, and small marks: a clock for a schedule, a pause for a paused schedule, a red mark when the last run failed. Edited replaces the age while you have unsaved changes

The list shows the 200 most recent of each status; a note says so when you are near the cap.

Right-click a row: Duplicate, and for an unsaved workflow Delete Unsaved Workflow…, for an edited one Discard Unsaved Changes….

Filter and sort

GroupOptions
StatusLive, Draft (not live yet), Not saved, Unsaved changes
RunsAny, On a schedule, Schedule paused, Not scheduled
ProblemsAny, Check finds problems, Last run failed (7 days)
TagsTags in use, with counts. Tags that would show nothing are left out
Uses a stepPick a step to list the workflows that use it. Needs a platform that can filter by step; otherwise the option reads coming soon
SortRecent, Name, Steps

Every option shows how many workflows it would leave.

Two views of one workflow

The Steps | Diagram switch in the toolbar changes how the same workflow is shown. Edits in one appear in the other, and undo/redo are shared.

Steps

A document read top to bottom.

SectionWhat it holds
Name and descriptionName this workflow, and an optional What does it do?
Starts withThe questions a run asks. Each has a label, a type and whether it is required. A question the steps read but the workflow never declared is tagged Found in this workflow; saving offers to declare it
StepsThe blocks, numbered. Add a step or the + between blocks opens the insert menu
ReturnsWhat whoever started it gets back, as named values
RunsHow it starts: When started, From an app (your apps can start it once exposed), or On a schedule (every N minutes, with the answers it starts with)

The insert menu:

ItemDoes
Step…Do something: look up, send, create. Opens the step picker
Ask a person…Wait for someone to approve or decide
Only if…Run the steps inside only when a condition is true
For each…Run the steps once per item of a list
Repeat…Run the steps again, up to a number of times, optionally until a condition holds

Data moves between steps as chips: a "Starts with" answer, an earlier step's result, or the current item of an enclosing For each. A text field can mix words and chips. A step's right-click menu has Only If…, For Each Item of a List…, Run at the Same Time as the Step Before, Stop Everything if This Fails, Add an Undo Step… (a rollback that runs if a later step fails), Duplicate, Move Up, Move Down, move in or out of a neighboring block, and Delete Step.

Diagram

The workflow as boxes and wires you can edit.

ControlDoes
Add a step listA palette of steps to drag onto the canvas. Hide it with the collapse button, show it again from the toolbar
Back / ForwardMove through where you have been (a block you opened, then out)
Wires: what runs after what / dataIn data mode wires show which result feeds which input, and you drag between them to map data
DirectionLeft to right or top to bottom
Technical namesShows the saved step names
Last runShows how the last run went on the boxes
Find a step (⌘F)Search the canvas
Selection barTogether (run these at the same time), In Order, Duplicate (⌘D), Discuss, delete (⌫)

Full page (⇧⌘F, Esc to leave) gives the diagram the whole window.

Other shortcuts, in both views: ⌘S saves, ⌘Z undo, ⇧⌘Z redo (Ctrl+Y also redoes outside macOS).

Side panels

The toolbar icons open one panel at a time beside the editor.

PanelShows
Run orderThe rounds the platform will run the steps in, from the compiled definition
Past runsRuns of this workflow, filterable by All, Finished, Failed, Running, newest 25. Every saved version runs as its own type, so the row says which version ran. Pick a run to see how each step went on the cards. Disabled until the workflow has been saved
Saved definition (JSON)What composition.save receives. Read-only
AssistantA chat about this workflow. See below

Checking

The editor checks as you type and again with the platform once edits settle (about a second).

CheckWhere it comes from
Problems marked on the boxesThe app's own rules, plus the platform's findings (composition.validate). A summary reads N things to fix before it can go live and scrolls to the first
Test runAsks the platform to validate the workflow and run the steps that only read, so nothing is sent or changed. The result reads passed or not, with what it could evaluate
Too largeThe platform's quick check caps its input at 16 KB. A bigger workflow says it is too large for the quick check

Saving, versions and live

Save (or ⌘S) stores a new version of the workflow. Unsaved edits are kept in this window until then.

OutcomeMessage
No changeNo changes to save — version N is current.
ValidSaved version N — it's live.
Not valid yetSaved version N as a draft. The platform found N things to fix before it can go live. A draft keeps the previous live version running

Before saving an existing workflow the app checks two things and, when either applies, shows one sheet:

  • Someone else changed it. If a newer version was saved while you edited, saving warns (Someone else changed this workflow) and Save Anyway saves yours as the newest; theirs is not merged.
  • What the save touches. Who uses this workflow, and the questions found in it that the save will declare. If a dependent still uses an older version, the result lists it.

A workflow opened from a definition the editor cannot round-trip opens read-only with the reason. Edit a Copy duplicates it; Edit anyway unlocks it.

Discard (in the status line, or from the row menu) throws away unsaved changes and returns to the saved version.

Running

Run… starts the live version for real: steps that send, create or change things will do so. It is disabled until the workflow is saved live and has no unsaved changes ("Save your changes first: runs use the live version"). The sheet asks the "Starts with" questions (required ones marked), then Run.

A bar under the toolbar follows the run: Running…, Finished or Failed: , with the run's ID. Show result prints the Returns values when the workflow declares them, otherwise its state without internals. The cards show each step's result, and failures are marked in red on the step.

Schedules

With On a schedule chosen, saving creates the schedule. The editor then shows Scheduled every N min · next with Pause, Resume and a delete that stops the schedule but keeps the workflow.

Every scheduled run is paid for, even when it finds nothing to do. Pick the slowest interval that works, and see Keep scheduled compositions cheap for cron times, change triggers and skip-empty conditions.

The assistant

Discuss with the assistant opens a chat in the side panel about this workflow. Each message carries context: the workflow's outline (including unsaved edits), its saved version and, when you select boxes on the diagram and press Discuss, which steps you are asking about. The assistant loads the saved version, proposes a change in its own working copy and tells you what changed; it never saves. You review its version in the builder and save it yourself. Starter prompts: Explain what this workflow does, What could go wrong when it runs?, Add a step that…. The chat is remembered per organization and workflow.

Workflows reach the platform through the same calls the web console and MCP use (composition.validate, composition.save, composition.activate, schedule.*), so a workflow saved here is the same object everywhere. See the workflow types registry.