ablative docs
↑↓ move↵ openesc close
Stack Notebook ablative.com.au

The console

Find authoring, launch, run history and operational views in the embedded console.

Open .md

Find a view

/
Hub: cluster, queues, workers and runs in the selected namespace.
/dashboard
Run counts, failures, workers, loops and server identity in movable tiles. Layout is stored in this browser.
/workflows
Find executions; open one by workflow id.
/workflows/:id
Read status, history, steps, children and transcripts, and use the authorized run controls.
/studio
Edit, check, format, document and deploy AWL.
/launch
Choose a deployed workflow and provide its typed input.
/definition/:workflowType/:contentHash
Read the immutable revision that a deployment or run names.
/triage
Health and operational diagnosis.
/settings
Server and namespace settings. The available actions depend on grants.

Use Studio to edit AWL and Launch to start a deployed workflow type.

Read a run

Choose a namespace, find a workflow and open its id. Read the pinned definition, step graph, event history and activity attempts together. A transcript belongs to a particular run, activity and attempt.

History records which worker served an attempt. Read connected workers for current registrations and unserved queues for current dispatch problems.

Connection state

The connection indicator reports whether the live stream is connected, reconnecting or disconnected. A possible gap is shown explicitly. Historical reads remain a separate source of evidence.

The command palette opens an entity or an operation’s page. Use the controls on that page to change a workflow.

The assistant

Open the assistant beside the page you are using. It shares one conversation across the panel and the editor’s inline entry. Read the assistant before giving it document changes.

Verify the server

A successful HTML response can be the console’s fallback for an unknown URL. Read a probe’s body and content type. Build identity, readiness and a workflow result answer different questions.

On main, apps/aion-ops-console/src/app/routes.tsx:90–107 binds the console screens. The server’s embedded asset and client-route handlers are in crates/aion-server/src/ops_console. Use the running binary’s console when evaluating its UI.