The Workflow Editor
The run screen: choose a workflow and a world, fill in the inputs or the canvas, run, pause, stop, resume, and read the run log.
The Workflow Editor is the screen where you run a workflow and watch the run. Its address is /p/<project-id>/workflow-editor. Open it with Execute Workflow on Home, or with a link from the CLI (see Links into the run screen).
Write workflows and canvases as project files and push them with zeon sync. See Authoring a workflow and Creating a canvas.
If a run is already live when the screen opens, for example after a page reload, the screen attaches to it: it selects the run's workflow and world and opens the Log tab.
The top bar
| Control | What it does |
|---|---|
| Workflow | Searchable list of the project's workflows. The refresh button beside it re-reads the list. |
| World and Load | Picking a world does not load it; Load does. While the picked world is not the loaded one, the bar shows "Not loaded: click Load to run" and Run stays disabled. |
| Deck | Opens a dialog of what sits on each seat of the world, where you can swap, place or remove plates and tip boxes. Read-only during a run. |
| Status badge | READY, RUNNING, PAUSED, COMPLETED, FAILED or CANCELLED. |
| Execution world | Simulation or Real Hardware. In the cloud only Simulation exists. Locked during a run ("Cannot change execution world during active execution"). |
| Reset (cloud) | Puts both simulated arms back at their start position, opens the grippers and lets go of a held object, without planning a move. It does not reload the world, and it is disabled during a run. zeon reset-arms does the same from the terminal. |
| Reconnect pipette (deployed box) | Reconnects and homes the pipette. |
| Run / Pause / Resume | One slot that changes with the run state. |
| Resume run | Continues an earlier run that did not complete. See Resume run. |
| Stop | Ends the run. Disabled when nothing runs. |
On first opening, the screen selects the workflow and world named as active in project.json, or the first in each list, and loads that world once per browser session.
The panels
- World View (left): the 3D view of the world the run uses, with a gizmo toggle. Under it, a collapsible Arm State strip gives each arm's tool centre point and joint angles; Auto re-reads them while the strip is open.
- Graph Editor (middle): the workflow graph. During a run the current step is highlighted, and a strip below the graph shows elapsed time, the status, completed steps against the total, the step in progress, finished steps with their durations, and on failure "Failed at" the step, with the error.
- The right panel has two tabs, Inputs and Log. Drag the dividers to resize the panels.
Inputs
Inputs shows an amber dot while required inputs are missing.
Without a canvas, the tab shows a form generated from the workflow's inputs, headed Workflow Inputs, with "All inputs set" or the number remaining. A workflow without inputs shows "No inputs defined." and "Ready for execution."
With a canvas, the canvas replaces the form. The canvas is the workflow author's own page; it has its own confirm button, often labelled Confirm setup. Run stays disabled until you confirm in the canvas. Depending on how the canvas is written, a later change in it can disable Run again until you confirm again. If the canvas cannot load, an amber card reads Canvas unavailable with the reason; Use standard form instead switches to the generated form for this session.
Values you enter are kept when you reload the page, and stay on screen after a Stop so you can run again with the same inputs.
Running
- Load the world you want with Load.
- Fill in the inputs, or confirm in the canvas.
- Click Run. A dialog titled Name this run opens, pre-filled with the workflow name. Change it or leave it, then click Start. A blank name gives the run a generated id.
Run is disabled while the workflow, the world or its objects are loading, while a canvas is unconfirmed, and while the picked world is not loaded.
Every run reloads the world before its first step, so it starts from the saved world, not from where the previous run left objects. A run changes nothing in the saved world.
One run at a time: if a run is already in force, a new one is refused with "Another run is in progress: … Stop it or wait for it to end."
On real hardware, Run first checks the wrist cameras and homes the pipette. See Running a workflow on real hardware.
Pause, Resume and Stop
- Pause stops the arms at once, mid-move, and holds the run. The badge reads
PAUSED. - Resume continues the paused run. A skill can offer its own resume choices; each appears as an extra button next to Resume, labelled by the skill.
- Stop stops the arms at once and ends the run; the run is recorded as cancelled and the badge returns to
READY. The arms stay where they stopped; nothing moves them to a rest position.
Prompts during a run
A skill can ask a question mid-run (ask_user_slack in the skill runtime API). A dialog opens over the screen with the question, any photos the skill attached, and one button per answer. It cannot be closed with Escape or by clicking outside: answering is the way out. If the box has Slack configured (see Secrets), the same question is posted to Slack, and whichever answer arrives first counts.
- While the run is paused, the prompt's timeout does not count down, and the prompt can still be answered.
- If the run is stopped while a prompt is open, the prompt ends at once and the run ends cancelled.
The run log
The Log tab, headed Run Log, shows the run as it happens. The screen switches to it when a run starts. A marker next to the heading reads Live, Connecting or Reconnecting. After a dropped connection the log reconnects on its own and fills in the entries written in between.
- Download .txt saves the whole log as a text file.
- The filter chips
all,notes,stepsandevents, and the search box, narrow the list. - Entries are grouped under each step, with its start time and its duration once done. Click a step to collapse it.
- When you scroll up, Jump to latest brings you back.
- During a run, the box at the bottom adds a note to the log (Enter sends, Shift+Enter adds a line). Notes are recorded with your email address.
The log shows step starts and ends, messages a skill writes with print_log(..., runlog=True), a skill's plain print_log output under its step, events, and notes. A failed run ends with FAILED and the error, which names the skill, the step and the line of the skill's code that raised (robotic_code.py:57).
Resume run
Resume run lists the workflow's earlier runs that did not complete, under "Resume an incomplete run", with their names, status and start time. It is disabled while a run is moving. It differs from the green Resume, which continues the run that is paused now.
Picking a run opens a five-step dialog:
- Resume this run? The world is cleared and reloaded, and the run's own inputs are restored.
- Hold the pipette: take hold of the pipette in the gripper.
- Open the gripper: sliders for each gripper.
- Return the pipette to its stand.
- Ready to resume: Resume starts it.
The sliders in step 3 send the gripper opening to the real grippers. On a deployed box, hold the pipette firmly before you move a slider, keep your other hand clear of the jaws, and move in small steps.
The resumed run keeps its name and run record and runs the workflow again from the first step. The log shows a "Run resumed" divider. Skills that record their own progress skip the work that run already finished; other skills run again.
Links into the run screen
The run screen reads three parameters from its address:
/p/<project-id>/workflow-editor?workflow=<workflow-id>&world=<world-id>&tab=inputs
| Parameter | Effect |
|---|---|
workflow | Selects the workflow. An unknown id shows "Workflow '…' is not in this project; showing the default." |
world | Selects the world. Without it, the world the simulation already has loaded is selected. |
tab | Opens the inputs or log tab. |
zeon app <workflow> --run prints such a link; zeon app <workflow> adds tab=inputs, where the canvas shows. The CLI prints it as a login link, /auth/link?code=...&next=<this address>, which signs the browser in once and then opens the address (zeon app needs CLI 1.5.5 or newer; see Login links from the CLI). Run zeon sync first: the link opens what your cloud instance has. See the CLI reference.
A link never clears a world the simulation already has loaded. When the screen was opened from such a link, while the page is open and visible, it re-reads the workflow and its canvas every 3 seconds and shows a new version when you push one, so an agent's changes appear as they land. A changed canvas starts fresh: confirm it again before Run. During a run, the screen waits for the run to end before it updates.
Updated about 19 hours ago