Workflow Detail
Workflow detail is the focused view of one selected workflow inside Mission Control.
This is where Agirunner starts to feel like an operator-grade orchestration system rather than a generic activity feed. You are no longer looking only at summary status. You are looking at the history, evidence, deliverables, and operator actions that explain how the workflow actually moved.
What Detail Includes
Section titled “What Detail Includes”For a selected workflow, operators can inspect:
- workflow state and lifecycle posture
- work-item hierarchy and board progress
- task activity and live console output
- deliverables and artifacts
- activations, history, and operator records
- steering, pause, resume, cancel, and repeat actions
Why It Matters
Section titled “Why It Matters”This surface is the bridge between control-plane state and execution evidence.
Without it, operators can see that a workflow exists but not:
- what the orchestrator has done recently
- which specialist task produced a result
- where human feedback should be applied
- what deliverable actually came out of the run
Major Detail Surfaces
Section titled “Major Detail Surfaces”The detailed workflow experience includes platform-owned views such as:
- an Orchestrator Activations card
- an Interaction Timeline for workflow events and packets
- board and stage presentation
- task graph and work-item review sections
- workspace timeline views
- operator flow controls and work-item metadata editing
That mix is intentional. Operators need both the execution story and the workflow-control story in one place.
Common Operator Actions
Section titled “Common Operator Actions”- open the live console to inspect runtime output
- review deliverables before closing the loop
- inspect history for routing or rework context
- steer a workflow with fresh operator guidance
- repeat or add work when the current path is insufficient
How It Connects To The Rest Of The System
Section titled “How It Connects To The Rest Of The System”Workflow detail is where high-level workflow state gets joined back to the underlying evidence and related product objects:
- it ties the selected workflow to its Workspace history and artifacts
- it exposes the orchestrator activations and task graph produced by the Orchestrator
- it gives operators direct paths into live execution evidence through Live Logs and runtime output
- it is where approvals, rework, and guidance from Approvals And Needs Action become actionable with full context
The workflow list tells you where to look. Workflow detail explains why the run moved, what it produced, and what intervention still makes sense.
When To Use This Instead Of The API
Section titled “When To Use This Instead Of The API”Use workflow detail when you need judgment and context. Use the API when you need integration and automation. The dashboard detail view is optimized for understanding and intervention, not for bulk orchestration by another system.