Module plan 

Execution plans – what a run would do, without doing it.

Ironflow workflows are Rust-native handlers, not declarative graphs: the only way to know which steps a run would create is to execute the handler with every step method short-circuited. That is what plan mode is.

A recorder is attached to a WorkflowContext by Engine::plan_handler. Every step entry point checks it first, records a PlannedStep, and returns a synthetic StepOutput without touching the store, the provider, the event bus or the network.

The success-shaped output assumption

Synthetic outputs are shaped like a successful step (exit_code: 0, status: 200), so a native if build.is_success() branch in the handler follows the happy path. A plan therefore shows the nominal branch, not every branch the run might take. Conditions declared with WorkflowContext::when are evaluated against the run input and reported; those declared with WorkflowContext::when_dynamic are reported as ConditionResult::Unevaluable.

Why the global dry-run flag is not used

ironflow_core::dry_run exposes a process-wide switch. Plan mode does not flip it: nothing is executed while planning, so the flag would buy nothing, and flipping a process-wide flag would corrupt real runs executing concurrently in the same process.

Structs

ExecutionPlan

The full plan for one workflow and one input payload.

PlanOptions

Knobs for Engine::plan_handler.

PlannedStep

One step the planner expects the run to create.

Enums

ConditionResult

Outcome of a branch condition as seen by the planner.

Constants

DEFAULT_ESTIMATE_SAMPLE_RUNS

How many past runs are sampled to estimate step durations.

DEFAULT_PLAN_MAX_DEPTH

How deep sub-workflows are expanded when the caller does not say.

MAX_PLANNED_STEPS

Hard cap on the number of steps a single plan may record.

Functions

estimate_durations

Average completed-step durations for a workflow, keyed by step name.