Dependencies, conditions, and checkpoints

Version 2 workflows use explicit graph edges between transaction steps, conditions, and manual checkpoints.

Add a dependency

Create an edge from the prerequisite node to the dependent node. A node becomes ready only after all required predecessors execute successfully. Graph position is visual metadata and does not change execution order.

Cycles are invalid because no node in the cycle could become ready.

Add a condition

Use a condition when readiness depends on current chain state:

• Balance: native or ERC-20 balance meets a threshold.
• Contract view: a saved view or pure function returns one supported value, then a boolean expression tests value.
• Block height: the latest block number satisfies a boolean expression.

txcast evaluates conditions through RPC after their dependencies complete. A false condition remains waiting and is checked again. Conditions cannot be manually passed.

Add a manual checkpoint

Use a checkpoint when an authorised human must confirm an explicit offchain prerequisite, such as a reviewed document or completed operational handoff.

1. Add a manual node with a precise title and description.
2. Connect its prerequisites and dependents.
3. Save the workflow.
4. During a run, the run owner completes the checkpoint after verifying its stated condition.

Checkpoint completion is recorded in the organisation audit log. It does not mutate the frozen transaction plan and should not be used as a generic “skip” action.

Recovery

If a condition stays waiting, check RPC/network health, the selected chain, contract ABI, and predicate. If the workflow logic itself is wrong, cancel the run and publish a corrected workflow revision.