An automation runs on its schedule or when you trigger it. This article covers how to run one, read the results in History, retry the Jobs that didn't succeed and stop a run.
Run on a schedule
Open the automation.
Switch on the Scheduler.
Select daily, weekly or monthly, and set the time.
Click Save.
Click Scheduled in the Automation menu to see every automation that is set to run.
Run it now
Open the automation.
Click the play button (Manually trigger this task).
Read the Manually Trigger Task check:
Line | What it tells you |
Running now will process N records | How many records match right now |
Last run | When this automation last ran |
Estimated completion | Roughly when the run will finish |
Errors | "This task cannot be run". Trigger now is disabled until you fix the problem |
Warnings | For your information. They don't stop the run |
4. Click Trigger now.
Note: Messages only go out inside the automation's Sending Window, whenever the run starts.
Do a demo run first
Open the automation and switch Demo Mode on.
Click Save.
Trigger it.
Click History and open the run.
Check the Jobs list shows the records you expected.
Switch Demo Mode off and click Save.
A demo run only checks the conditions. Each matching record is listed as a Job with the note "Skipped: demo run, nothing was created or sent". No emails, SMS, forms or tasks are created. The run shows a Demo tag.
Check History
Click History in the Automation menu.
Runs that haven't finished are listed first, then the newest. Each row shows:
Item | What it tells you |
Name | Which automation ran |
Triggered by | A staff member's name, or Automation Service User for a scheduled run |
Jobs | How many records it processed |
Time | How long it took to process, such as |
Status | See the table below |
Outcome | "All jobs completed successfully", or "N of M jobs did not complete successfully" |
Retry tag | The run is a retry of an earlier run |
Demo tag | The run was a demo run |
Run statuses
Status | Meaning |
Scheduled | The run is queued and will start soon |
Processing | The run is working through its Jobs |
Awaiting Feedback | Every Job is processed. The emails and SMS are scheduled and the run completes when they have all been sent |
Completed | The run has finished |
Failed | The run stopped because of an error |
Cancelling | The run is being stopped |
Cancelled | The run was stopped |
Note: Awaiting Feedback is not a stuck run. With a Sending Window it can last hours or days.
Read one run
In History, click the run.
Three cards show the results:
Card | Counts |
Jobs | Pending, Processed, Warnings, Failed, Cancelled |
Emails | Pending, Sent, Failed, Cancelled |
SMS | Pending, Sent, Failed, Cancelled |
Job results
Result | Meaning |
Processed | Everything the Job tried to send was sent |
Warnings | Part of it got through, for example the email sent and the SMS did not |
Failed | Nothing got through |
Cancelled | Everything was cancelled before it was sent |
Waiting | The messages are scheduled and haven't reported back yet |
Run details
Field | Meaning |
ID | The run's reference. Quote it to support |
Triggered By | Who or what started the run |
Retry Of / Retried By | Links to the run this one retried, and to runs that retried this one |
Started | When the run began processing Jobs |
Process Time | How long it took to process the work |
Run Time | The whole run, including the wait for emails and SMS |
Completed | When every Job finished |
Messages | Notes from the run, such as why it stopped |
2. Use the state filter on the Jobs table to show only Failed or Warnings.
3. Read the log table for the reason, such as a patient with no mobile number.
Tip: A healthy run has Processed equal to the number of records matched, with Warnings and Failed at 0.
Note: If a Send Form action can't reach the patient at all, the form is archived. The Job shows "Form archived: none of its emails or SMS could be sent".
Find one patient's Job
Click Jobs in the Automation menu.
Filter by state, or find the patient in the list.
Jobs lists every Job across every run.
Retry the Jobs that didn't succeed
A finished run with Jobs that failed, were cancelled or ended with warnings shows a Retry button.
Fix the cause, such as adding the missing mobile number.
In History, click Retry on the run.
Tick the Jobs to reprocess. Failed and Cancelled are ticked. Processed (with warnings) is optional.
Click Retry N jobs.
Zavy starts a new run of the same automation for those Jobs only. The new run shows a Retry tag.
Note: A retry does not check the conditions again. Patients who already got the message are not sent it twice, and no new patients are added.
Note: You can retry a run again once its earlier retry has finished.
Stop a run
In History, find the run that is still in progress.
Click Stop run.
Confirm.
Every email and SMS not yet sent is cancelled, including those scheduled for later in the Sending Window. A message shown as Cancelled did not go.
Warning: Messages already sent can't be recalled.
Tip: Use Retry later to pick up the Jobs a stopped run didn't finish.
Messages you may see
Message | Meaning | What to do |
"No records found to process" | The conditions matched nothing on this run | Nothing, if that is expected. Otherwise open the automation and click Check Conditions |
"Unable to schedule, a task is already in progress" | The previous run of this automation had not finished | Wait for the next run. If a run looks stuck, stop it |
"This task cannot be run" | The automation has a problem, such as no conditions or no action | Open the automation and fix it |



