Testing and run history
Every automation keeps a history of what it did, step by step, and Test shows what it would do before it does anything real. This page covers the test, the run history of one automation, the Activity of all of them, when Quanty pauses an automation, the limits and the credits.
Before you start
- Testing needs edit access to the project; reading the history only needs access to the project (see Automations).
- A test that really runs (with Dry run off) also needs edit access to the table, because it may change it.
Test an automation
- Open the automation and click Test in the top bar.
- Under Record, keep Latest record or pick one with Choose a record.
- Keep Dry run on: "Nothing is sent or written." Off: "The actions really run: notifications, e-mails, table changes."
- Click Run test.
The result shows whether the record meets the conditions (for example Conditions not matched), then each step with its status and what it would do: "Would send 1 e-mail" with From, To and Subject. In a dry run every step is Simulated. A test runs even when the conditions do not match, so you can check the steps on any record.
- With an E-mail received trigger: "The test uses the newest e-mail in the mailbox, or a sample one when none has arrived yet."
- A real run of an automation that runs AI columns is blocked while AI is off for your organization.
- Test runs are kept in the history with a Test mark.
Run history
History in the top bar (or Run history in an automation's ⋯ on the Automations page) lists its runs, newest first, with a Test mark on test runs.
Click a run to see its steps.
| Run status | What it means |
|---|---|
| Queued | Waiting to start. |
| Running | Working through its steps. |
| Succeeded | Every step that ran finished. |
| Failed | A step failed; open the run to see which and why. |
| Skipped | It did not run, with the reason (for example the WhatsApp window was closed or there were no credits). |
| Step status | What it means |
|---|---|
| OK | The step did its work. |
| Failed | The step failed. With Stop on error on, the steps after it are skipped. |
| Skipped | The step did not run, with the reason. |
| Simulated | A dry run: nothing was sent or written. |
The history shows 50 runs at a time and keeps runs for 30 days.
Activity of all automations
Activity on the Automations page opens Automation activity: what every automation did.
| Filter | Choices |
|---|---|
| Show activity from | In this project or Whole workspace. |
| Status | All, Succeeded, Failed, Skipped, Running. |
| Period | 24 hours, 7 days, 30 days. |
| Automation | All automations or one. |
| Trigger | Any trigger or one kind. |
| Switches | Only e-mail automations and Test runs. |
"When an automation runs, what it did shows up here." Clear filters resets them.
When an automation pauses
Quanty does not switch an automation off because of failed runs: it keeps running, and each failure shows in the history and as Last run failed on the Automations page. It pauses an automation only when it cannot work at all:
| Reason | What to do |
|---|---|
| "Paused: the AI budget ran out." | A Run AI columns step found no credits. Top up or wait for the new month, then switch it on. |
| "Paused: its mailbox was disconnected." | Pick another mailbox in the trigger or step, then switch it on. |
| "Paused: its mailbox is no longer shared." | The person who connected the mailbox stopped sharing it; its owner should check the steps and switch it on. |
| The WhatsApp number was removed | Pick another number, then switch it on. |
Switching a paused automation on again clears the reason.
Limits
| Limit | Value |
|---|---|
| Runs of one automation | Runs per hour, 60 by default, at most 1 000 |
| Steps in one automation | 10 |
| Conditions | 20 |
| Recipients of one step | 100 |
| Rows in a schedule digest | 200 |
| AI rows per automation a day | 200 |
| E-mails | 200 an hour per organization, 100 an hour per mailbox |
| WhatsApp messages | 200 an hour per organization |
| SMS | 30 an hour and 1 000 a month per organization |
| Automations starting each other | 3 deep |
| Run history | 30 days |
Credits
Most of an automation costs nothing. These steps spend your organization's credits (see Credits and usage):
| Step | What it costs |
|---|---|
| Run AI columns | The AI work for each row, like a run of the table (see Columns and AI). |
| Send a WhatsApp message | Per message, from what the message costs WhatsApp, plus 30 %. To a Polish number, free text in the 24-hour window is about 7 credits and a template about 29 credits. |
| Send an SMS | Per SMS part, plus 30 %. To a Polish number, about 42 credits. The SMS page shows the price per SMS. |
| Notify people, Send an e-mail, Update the record, Create a record | Nothing. |
The cost of WhatsApp and SMS shows on the Usage page under their own categories. A WhatsApp or SMS step is skipped while the organization cannot spend credits.
Good to know
- No undo. A run cannot be undone from its history: what it sent is sent, and what it wrote stays until someone changes it. Use Dry run first.
- Deleting keeps the history. "The automation will be switched off and deleted. Its run history stays."
- Test on the record you mean. Choose a record lets you test the record that should match, and a different one that should not.
Related pages
- Automations: the Automations page and the builder.
- Triggers and conditions: limits and behaviour of the trigger.
- Actions: what each step does.
- Credits and usage: credits, budgets and the Usage page.