Runs And Outputs
Breyta operations guide for post-change smoke checks, output validation, and incident triage.
Quick Answer
After push/configure changes, run breyta flows run <slug> --wait, inspect final output shape, and confirm expected side effects. For public/end-user flows, also open the Output page and verify that the first artifact is the intended human-readable result.
For output shaping rules, use Output Artifacts.
The normal rich result pattern is a Markdown report, optionally with
breyta-resource fences for embedded tables, charts, downloads, media, nested
Markdown, or JSON resources.
Do This Now
| Step | Action |
|---|---|
| 1 | Start a run for the flow target you just changed. |
| 2 | Wait for terminal state and inspect run details. |
| 3 | Validate output contract keys/types used by consumers. |
| 4 | Confirm expected external side effects completed. |
| 5 | For public/end-user flows, inspect the Output page for human readability. |
breyta flows run <slug> --input '{"n":41}' --wait
breyta runs show <workflow-id> --pretty
To inspect creator-facing run cost estimate data, include all steps:
breyta runs show <workflow-id> --steps 0 --pretty
The run response includes aggregate and step-level cost estimates when the run has priced lines. Use Run Cost Estimates for :metering, token pricing, and breakdown fields.
What This Confirms
| Check | Signal |
|---|---|
| Current target is active | The expected runtime target is reachable. |
| End-to-end execution path | Trigger-to-output path works in real runtime conditions. |
| Output contract stability | Consumers receive expected keys/types. |
| Integration health | External writes/actions happened as expected. |
Public Flow Output Checks
Public manual-run output should be readable without opening debug data or knowing the internal schema.
| Check | Passes when |
|---|---|
| Primary artifact | The first viewer item is readable markdown by default, or a deliberate table/media viewer when that is better for the user. |
| Table columns | Any separate table viewer uses human labels such as Who, Followers, Contact, Link, and Why relevant. |
| No raw debug panel | There is no default :raw viewer or Structured output panel unless structured data is the product output. |
| No internal refs | Top-level res:// table refs, persisted run-table refs, and automation-only maps are not visible in the public result. |
| No implementation fields | Internal fields such as top_candidates_preview, status counters, trace ids, and table ids are not visible to end users. |
| Embedded resources | Markdown breyta-resource embeds render in place; users do not see raw fenced blocks or technical resource URIs. |
| Structured detail | EDN/JSON maps appear as a raw viewer, JSON resource embed, or fenced code block, not as one-line paragraph text. |
If a flow needs both public presentation and machine-readable automation data, persist the automation data as resources or tables and return only the curated presentation in the final public output.
Incident Checklist
| Step | Action |
|---|---|
| 1 | Identify failing step from run timeline. |
| 2 | Verify required connections/secrets/inputs are configured for the runtime target. |
| 3 | Isolate and reproduce failing step behavior. |
| 4 | Decide retry, cancel, rollback, or compensating follow-up flow. |
Inspect persisted artifacts with breyta resources ... by listing workflow resources and reading res:// refs.
Advanced/Release Validation
For broader scenario coverage (failure matrix, CLI/API regression checks, release evidence), use your integration test suite and release validation checks.