Agiled Docs

Simulation helps you check the structure of a workflow before using it for real customer or finance work.

Use simulation for every workflow that creates records, sends notifications, updates finance data, or touches customer-facing communication.

Use testing as a staged rollout. Simulate first, run one safe record second, and only then publish or enable the workflow for normal volume.

Run A Simulation

Open the workflow builder.
Open the simulation panel.
Run the simulation.
Review each simulated step.
Check branches, delays, and repeated steps.

Simulation can show the path through the graph and the records available from the trigger context.

The simulation panel can show simulated steps, branch decisions, and context sections. Use it to confirm that a condition chooses the expected true or false branch and that later actions can see the records they need.

Simulation should be part of building, not a final checkbox. Run it after adding conditions, delays, loops, provider actions, or customer-facing messages.

Test With Safe Data

After simulation looks correct, trigger the workflow with safe test records and review the run history.

Run the smallest realistic test first. One safe record is enough to confirm the workflow path before using live volume.

Use test data that includes the edge cases your workflow depends on, such as a missing email, unpaid invoice, high-value deal, empty custom field, or multiple records in a loop.

What to Check

The trigger payload has the fields your workflow expects.
Conditions take the correct branch.
Delays and For Each nodes appear in the expected order.
Variables resolve from trigger data or previous steps.
Created records have the correct owner, status, due date, and relationship.
Customer-facing messages use safe copy and correct recipients.

Simulation vs Real Run

Simulation proves the graph shape and available context. A real test run proves the provider calls, permissions, record creation, notifications, and side effects. Use both before publishing high-impact workflows.

Do not rely on simulation alone for workflows that send email, post to Slack, create finance records, call integrations, or update customer-facing records.

Safe Test Data

Use test contacts, test projects, draft invoices, internal email addresses, and private channels. Avoid using real customer records until the run detail proves the automation behaves correctly.

Troubleshooting

If simulation passes but the real run fails, check permissions, connected app state, missing records, and action-specific validation.

If the wrong branch runs, inspect the condition inputs in run detail instead of guessing from the builder alone.

If a test run creates unwanted records, pause the workflow, clean up the test records, and adjust the workflow before running another test.

Test Checklist Before Publishing

Before publishing a workflow:

Simulate the expected path.
Simulate or test each branch.
Run one safe real record.
Review run detail and step outputs.
Confirm notifications, records, and integrations behaved correctly.
Clean up test records.
Document what the workflow should do when it fails.

For workflows that send messages or create finance records, ask a second person to review the test output before activation.

Simulate And Test Workflows