Execution and Monitoring
After you build a workflow, BizOps Engine records runs so operators can verify outcomes and troubleshoot failures.
What a run looks like
A job execution typically captures:
| Field | Meaning |
|---|---|
| runId / cycleId | Unique identifier for the run |
| triggerSource | What started the run (manual, event, schedule, and so on) |
| startTime / endTime | Wall-clock span of the run |
| duration | Elapsed time in seconds (or equivalent) |
| result | Overall outcome (for example Success) |
| stepTrace[] | Per-step timing, status, and optional output |
Execution logs
During a run, the engine emits ordered log events. Useful log attributes include:
| Attribute | Use it to |
|---|---|
| timestamp | Reconstruct sequence |
| severity | Separate info from warnings and errors |
| message | Read human-facing progress |
| stepId | Correlate the log line to a canvas step |
For the mock observability demo, logs commonly include source topic/signal details, AI diagnosis confidence, and remediation dry-run output.
Cycle history screen
Open cycle history from a job when you need the full narrative of a run:
- Confirm overall result and duration.
- Expand the stepTrace to see which step failed or slowed down.
- Inspect step output payloads used by downstream steps or dashboards.
- Compare against an earlier successful cycle when diagnosing regressions.
Monitoring checklist
| Question | Where to look |
|---|---|
| Did the job start? | Job status / latest cycle entry |
| Which step failed? | stepTrace status values |
| What did the step return? | Step output on the failing or prior step |
| Was the trigger wrong? | triggerSource on the cycle |
| Is this environment-specific? | Job environment + version fields |
Demo vs production execution
| Mode | Behavior |
|---|---|
| Mock / demo path | Deterministic logs and outputs for UI walkthroughs; no real Kafka, AI inference, or process kill |
| Integrated deployment | Steps execute through configured plugins / Orchyron bindings against real systems |
Always confirm which mode your environment uses before interpreting remediation-style actions as real side effects.
Connecting runs to Dashboard Hub
Operational and business dashboards in Dashboard Hub can visualize BizOps-oriented metrics through the BizOps data source type and related APIs. Use Engine for authoring and run forensics; use Dashboard Hub for fleet-level and stakeholder views.