Runs and versions

Workflow versions

Every deployment creates an immutable, incrementing version and makes it active. Deploying unchanged source still creates a version. Concurrent deployments allocate distinct versions.

Invocation captures the active version before execution, so a later deployment does not change a run already in progress. The current API does not provide a version-selection or rollback endpoint.

Recorded runs

The service persists input, decisions, output, trace, timing, and status. Status is running, completed, or failed. Inspection includes the stored input; list responses omit it.

Set BANH_API_URL to the API origin, BANH_ACCOUNT_ID to your account, and BANH_API_TOKEN to a valid developer token. Invocation keys cannot list or inspect runs.

List workflow runs

curl --fail-with-body --silent --show-error \
  -H "Authorization: Bearer $BANH_API_TOKEN" \
  "$BANH_API_URL/v1/accounts/$BANH_ACCOUNT_ID/workflows/warranty_triage/runs?limit=50&offset=0"

Results are newest first. limit defaults to 50 and accepts 1–100; offset defaults to 0 and accepts 0–10000. The response contains runs, limit, and offset.

Inspect one run

Set BANH_RUN_ID to an ID returned by invocation or listing:

curl --fail-with-body --silent --show-error \
  -H "Authorization: Bearer $BANH_API_TOKEN" \
  "$BANH_API_URL/v1/accounts/$BANH_ACCOUNT_ID/runs/$BANH_RUN_ID"

Failure behavior

Timeouts persist a failed run. Late backend completion cannot overwrite that failure, but the current backend interface cannot cancel inference already in progress.

Process termination can leave runs marked running; crash recovery is not implemented. See limits and troubleshooting for current constraints.