Use an Automation's Executions tab to see whether a record triggered it, when a scheduled email is due, and why a run was skipped, cancelled or failed.

Before you start

• Sign in to the Vizmo portal as an administrator and select your location. The Automation menu is not shown to employees or receptionists.
• Create and save the Automation first. History appears only after a record has matched it.
• Availability: if this option is greyed out or missing, contact your Vizmo account manager.

Which page do I use? Use Automation > Logs for a table of Automation activity across the location (name, start date, end date, status and action type). Use the Executions tab on one Automation to see why that Automation did or did not send.

Open the execution history

1. Open Automation > Workflows and select the Automation.
2. In the details panel, select the Executions tab.
3. Use Terminal history to choose Past day, Past 7 days or Past 30 days. This list covers runs that have finished. Runs still in progress always show. The default is Past 7 days.
4. Read each card: Source (the record that triggered it), Schedule, Due/completed and Status. Times use your location's time zone.
5. Select Show details to see each step, its due time and, if it did not run, the reason. Select Hide details to collapse it, or Load more to see older runs.

What each status means

• pending: the run is still in progress. A step can be waiting, scheduled or running. Check the due time before treating it as late.
• completed: the run finished. This does not show whether the recipient read the email.
• skipped: the step did not run. The reason is in the details.
• cancelled: the run or step was cancelled. Check the record and the Automation before you assume anything was sent.
• failed: the run or step failed. Check the details and the Email Alert or Webhook settings.
• Details unavailable: the run exists but its details could not be loaded. Select Retry to load the history again. Retry does not resend anything.

Why a step was skipped or stopped

The reason appears in the details of a step. Use this table to read it.

What you see	What it means
initial-action-rules-not-matched	When the record was saved, it did not meet the conditions for this email, so the email was never scheduled.
initial-skip-rules-matched	When the record was saved, it met a skip condition, so the email was never scheduled.
invalid-anchor	The date the email is based on is missing or not usable on the record, so a due time could not be worked out.
missed-before-date	The email was set to go out before a date, and that time had already passed when it could be scheduled.
recurring-source-not-supported	The email is based on a repeating record, which scheduled emails do not support.
source-not-found	The record the email was based on no longer exists.
source-became-terminal	The record was already finished or cancelled, so the email was not sent.
workflow-not-found or workflow-disabled	The Automation was deleted or turned off before the email was due.
action-not-found or unsupported-current-action-kind	The email step was removed or changed to a type that cannot run on a schedule.
workflow-rules-not-matched	When the email was due, the record no longer met the Automation's conditions.
action-rules-not-matched	When the email was due, the record no longer met the conditions set on this step.
skip-rules-matched	When the email was due, the record met a skip condition.
dependency-not-completed	A step this one waits for did not finish.
immediate-action-failed or email-delivery-failed	Vizmo could not complete the step or send the email. Check the recipients or the Webhook receiver.
cancelled	The run was cancelled.

If you see any other reason, contact support@vizmo.in with the Automation name and the reason shown.

If you change a scheduled email

• If the date a pending email is based on changes on the record, Vizmo reschedules the email. The step details show the new due time.
• If you edit the Automation's timing, only new records use the new timing. Existing runs keep the timing they started with.

Troubleshooting

• No executions yet. Check that a record has matched the Automation's module, event and conditions. For an approval condition, the approval must newly change to Approved. For older finished runs, choose a longer Terminal history period.
• History does not load. Select Retry. If it still fails, contact support@vizmo.in with the Automation name and the error shown.
• A scheduled step is still pending. Compare its due time, shown in your location's time zone, with the current time.

To create the Automation in the first place, see Create an email automation.