Validation and simulation
Validation checks whether a definition can be executed. Simulation follows one route with a supplied payload while suppressing external effects.
Validate the graph
The builder validates while you work and shows either Valid or an issue count. Resolve issues before publishing. Common causes include a missing trigger, an incomplete node configuration, a route without a destination, an unsupported decision connection or a graph that cannot reach an End node.
Validation proves structure and configuration. It cannot prove that a real Magento event will carry the values assumed by a rule or that an external endpoint will be available.
Run a simulation
- Save the current definition.
- Click Simulate.
- Start with an empty payload, select a privacy-safe recent run, or paste JSON that matches the trigger contract.
- Run the simulation.
- Compare the reported steps with the intended route.
Recent-run payloads may contain customer or order data. Use them only with the separate payload-view permission and avoid copying them into tickets or public documents.
Expected stopping points
A Human Task stops simulation at the task node without creating an Admin task. A Wait records its resume information and stops the simulated path without scheduling a live continuation. Email, webhook, entity-update and comment actions do not perform their external side effect during simulation.
This behavior lets you inspect routing safely, but it also means simulation cannot replace an end-to-end test.
Minimum pre-publish check
Simulate every condition, switch and decision route with representative values. Then publish and run one controlled Magento event through the real queue, task and cron path. Record the definition code, event, expected route and resulting run status so a later failure can be compared with a known-good run.