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.

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.

breyta flows run <slug> --input '{"n":41}' --wait
breyta runs show <workflow-id> --pretty

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.

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