# Runs and results

Source: https://openflow.run/en/docs/concepts/runs/
Language: en
Product version: 0.1.0-beta.77

Inspect an accepted execution, its node invocations, pending decisions, and final business result.

A Run executes one selected entry using a fixed definition and configuration. The same Flow can have many Runs, each with its own inputs, node results, decisions, and terminal status.

## Inputs and node results

Inspect node inputs to see the values actually collected on the selected execution path. Inspect outputs to see the result committed after validation. A latest-result view is useful for inspection; it is not a source that other nodes can use to bypass data dependencies.

Outputs declares the final workflow business result. Logs, node results, and workflow outputs have separate roles and retention contracts.

## Waiting

Wait and Approval suspend a local branch within the same Run. Other ready branches can continue. The accepted decision resumes that branch; it does not create a replacement Run.

Wait suspends this branch until a continuation is accepted; the same Run then returns its result.

**Input**
Start the workflow, then continue the pending Wait.

**Expected result**
{"message":"Review finished"}

**Before running**
An Open Flow deployment is needed to execute or import this example. The preview itself runs offline.

[Download workflow](https://openflow.run/docs/examples/wait-and-resume.openflow.json)

A Wait or Approval decision uses its Run and Wait identities. The first accepted decision wins. Repeated submissions do not overwrite it or queue another continuation.

## Terminal outcomes

A successful Run completed its selected work. A failed Run has a confirmed failure. Cancellation and deadline expiry have their own outcomes. An indeterminate result means that the deployment cannot confirm whether an external effect completed.

Inspect those distinctions before retrying. A failed downstream step does not imply that earlier external writes were rolled back.

## Recovery and retention

A deployment persists recovery facts such as completed results, Waits, and supported Agent continuations. Recovery follows the execution contract and must not repeat an unconfirmed side effect to reconstruct missing data.

Terminal results and decision receipts are retained independently of ordinary event logs. The deployment owns retention periods and resource limits. See [deployment responsibilities](https://openflow.run/en/docs/reference/deployment/index.md).

## Sources

*   [docs/control/contracts/control-api.md](https://github.com/oomol-lab/open-flow/blob/e25a738d170322734572a0b8a1323cb00b9d355a/docs/control/contracts/control-api.md#5-run)
*   [docs/architecture.md](https://github.com/oomol-lab/open-flow/blob/e25a738d170322734572a0b8a1323cb00b9d355a/docs/architecture.md#wait-and-agent)