Monitoring automation runs

Last updated: September 2, 2026

Every time an automation runs, Edvisor records a log entry. This article covers where to find the logs, what each log entry contains — including the Trigger column, which can show any of the available events — and common reasons an action might fail. It also explains why a duplicated automation shows no runs until it is enabled.

Every time an automation runs, it records a log entry. This article explains where to find those logs, what each field means, and how to read them when something goes wrong.

Automations can be started by a wide range of events — student, proposal, enrollment, sales and insurance events — so the logs for any given automation reflect whichever trigger it was built on. The fields, statuses and failure reasons below are the same regardless of which trigger fired.

What it is

A log is the record of a single automation run. Each run creates one log entry, so you can see exactly what happened, when, and whether it worked. Logs cannot be edited or deleted — they are a permanent record.

Where to find the logs

  1. Go to Settings > Recruitment > Automations.
  2. Open the automation you want to check.
  3. On the Edit Automation screen, switch from the Automation tab to the Logs tab.

If the automation has never run, you see an empty state that says "No executions yet" with a button to view the automation configuration.

Reading the logs

The Logs view shows:

  • A Status filter (for example, "All statuses") to filter runs by result.
  • A counter showing how many runs are listed (for example, "Showing 12").
  • One row per run.

Each log row shows these fields:

  • Time — when the run happened.
  • Status — the result (see below).
  • Trigger — the event that started the run. This is whichever trigger the automation was built on, so it can be any available event. Examples you may see include Proposal created, Proposal Issued (previously called Proposal Published), Proposal Viewed, Proposal Accepted, Proposal expiry date, Pipeline Stage Change, and the insurance triggers Policy start date and Policy end date.
  • Execution ID — a unique ID for the run (starts with "exec-"). Reference the Execution ID when reporting an issue, so the exact run can be found.
  • Actions — how many actions ran, as a ratio (for example, "1/1" or "0/1 skipped").
  • Duration — how long the run took.

Click a row to expand it and see details for each action in that run.

Statuses

  • Success — the automation ran and all actions completed.
  • Failed — the run did not complete.
  • Partial Failure — some actions completed and some did not.

Where runs also appear

Automation runs also show up on the student's Recent Activities feed, so you can see automation activity from the student's profile.

Common failure reasons

If a run fails, it is usually one of these:

  • The webhook returned a non-2xx response.
  • The webhook URL pointed to an internal or private IP address (these are blocked).
  • The webhook followed more than 5 redirects.
  • A required variable could not be filled.

Why an automation might have no runs

If the Logs tab is empty when you expected entries, check whether the automation is switched on. In particular, when you Duplicate an automation from the card menu, the copy arrives switched off, with a banner on the automation saying so. A disabled automation never runs, so it produces no log entries at all until you enable it. This is the most common reason a newly duplicated automation appears to be doing nothing.

It is also worth confirming that the trigger has actually occurred and that the conditions on the automation match the records you are expecting — a run is only logged when the trigger fires and the conditions pass.

When to check the logs

Check the logs when an expected email, task, or webhook did not happen, or when someone reports that an automation is not working. The status and the expanded action details tell you which step failed and why.

Related