Test, Backtest and Activate a Workflow
Test a saved workflow first, backtest it to see how many messages it would have caused, then activate. If an edit breaks it, restore an earlier version.
Test a workflow
- Open the saved workflow and choose Test.
- Use the sample data, or load a recent real event.
- Check whether the workflow would start, how each condition evaluated, and what each step would receive.
Nothing is sent, saved or changed. Some steps behave specially in a test:
- Find record does run, because it only reads, and the path uses what it found.
- Wait for event is simulated: choose Happened or Timed out. The test does not pause.
- Request approval is simulated: choose Approved, then Rejected.
- Loop walks Each once and then Done, and does not send.
- AI Step is not run; use Try it on the step instead.
The test checks the saved version. For a workflow with branches it shows the path the run would take and highlights it on the canvas.
Backtest: see what it would have done
- In Test, under Backtest, choose the last 7, 30 or 90 days.
- Press Run backtest.
Using your real data, Biznsbook shows how many times the workflow would have run, how many runs conditions or run rules skipped, how many emails and WhatsApp messages it would have sent to how many people, a bar for each day, and some examples. Nothing is sent. A workflow run by hand or by a nothing-happened check cannot be backtested.
Activate
- Choose Activate. As a Builder, choose Save & request activation and a manager reviews it.
- Activation checks every step's settings, the schedule or date check, and that your company has the modules each step needs. It refuses a workflow that contains a Coming soon action.
- If the workflow would have messaged more than 50 people on one day in the last 30 days, you see the numbers first and confirm.
- Do the real business action and check Automation → Runs.
See and restore an earlier version
- Open the workflow in the visual builder and choose More → History and restore.
- Compare shows what differs from the newest version. Restore brings an older one back.
From Runs, the Workflow version number on a run opens this list at the version that run used. Restoring saves it as a new version and leaves the workflow off until someone with the right to activate switches it on. The newest 100 versions are kept.
:::tip Always backtest message workflows A reminder workflow can reach many customers at once. A backtest shows the numbers before anyone gets an email. :::
Related articles
Learn more about Biznsbook Automation on biznsbook.com.