Action simulation

Action simulation tests whether a prepared batch of actions is likely to succeed through its intended execution route. Authors and reviewers can check execution permissions and the calls' effects before the account executes them.

The app offers simulation during proposal creation and on an existing proposal, where the action batch and process determine the route. The direct create-transaction flow offers the same capability using the connected actor's execution context.

What it simulatesCopy Anchor Link

The simulation reduces the intended execution to an action array plus its caller and account context. In a governance-routed flow it simulates execute on the DAO with the process's plugin as caller — the staged proposal processor itself in a multistage process. In a direct-execution flow, the connected actor is the caller and the DAO is the target.

No proposal object enters that simulation: it deliberately bypasses proposal creation, metadata, status, voting, approval, and every other governance step to test the permission and action-execution path: whether the intended caller is permitted to execute, and whether the actions themselves succeed.

The app runs the simulation on Tenderly: the UI shows a likely-to-succeed / likely-to-fail verdict and links out to the Tenderly results. Simulation requires the app's Tenderly integration for the selected chain; Supported chains lists its availability separately from account creation.

Where it is availableCopy Anchor Link

• During proposal creation, after the action builder has prepared the batch and before the proposal is submitted. The selected process supplies the execution context. The author can skip simulation or continue after a likely-to-fail result.
• On an existing proposal, where the actions are already bundled and the owning process supplies the execution context. The Proposal details page controls when simulation is available and when a result can be refreshed.
• During direct transaction creation, after the action builder has prepared the batch and before it is submitted. The user may run or skip the simulation; the connected actor supplies the execution context.

Why this is the meaningful questionCopy Anchor Link

An author, reviewer, voter, or signer needs to know whether the prepared actions will work through their intended execution route and what they will do. Simulating an earlier wrapper call is not equivalent: a Safe-side simulation of a direct proposal-creation grant can show that the Safe may call createProposal while saying nothing about whether the bundled actions will succeed later (see direct creation grants to a Safe). Action simulation asks the execution question directly.