Monitoring automation runs

Every time an automation runs, Edvisor records a log entry. This article covers where to find the logs, what each log entry contains, and common reasons an action might fail — so you can confirm automations are working and troubleshoot when they aren't.

Every time an automation runs, Edvisor records a log entry. Use the logs to confirm your automations are firing as expected and to troubleshoot when something isn't working.

Where to find logs

Open an automation from the Automations list. On the Edit Automation page, switch from the Automation tab to the Logs tab.

The Logs view shows:

• Status filter — narrow logs to a specific status, or leave at "All statuses" to see everything.
• Counter — the total number of log entries matching the filter ("Showing N").
• A row per execution showing its time, status, trigger, execution ID, actions, and duration.

If the automation hasn't run yet, you'll see a No executions yet message — "When this automation runs, every execution will appear here with its status, actions and duration" — with a View automation configuration button to jump back to the builder.

What's in a log entry

Each row in the Logs view shows:

• Time — when the automation fired.
• Status — Success, Failed, or Partial Failure (see below).
• Trigger — the event that started the run (for example, "Quote created").
• Execution ID — a unique ID for that run (for example, exec-07f6fec17-…). Quote it when reporting an issue so the exact run can be found.
• Actions — how many actions ran, shown as a ratio: 1/1 when every action ran, or 0/1 when an action was skipped (the skipped action is flagged). A skipped action isn't the same as a failure.
• Duration — how long the whole run took.

Expand a row to see each individual action in that run and how long each one took.

Statuses:

• Success — every action in the sequence completed.
• Failed — the run couldn't start (for example, a configuration issue prevented execution).
• Partial Failure — the run started but at least one action failed while others succeeded. Actions run independently, so the failure of one doesn't stop the others.

Logs are immutable — they can't be edited or deleted, so you always have a permanent trail of every run.

Where runs also appear

When an automation runs for a student, the run is also recorded on that student's Recent Activities feed on their profile. You can see what fired for a student directly from their profile, without opening the automation's logs.

Common failure reasons

• Send Webhook action returned a non-2xx response. The log shows the response status from your endpoint.
• Send Webhook attempted to call an internal or private IP, which Edvisor blocks for safety. Use a public URL instead.
• Send Webhook hit more than 5 redirects. Edvisor stops following redirects at the 5th hop.
• A required variable couldn't be resolved at run time and the destination required it (for example, a webhook payload referencing a field that's empty on the student profile).

When to check the logs

• After enabling a new automation, check after a few expected events to confirm it fired and succeeded.
• If a student reports they didn't receive an expected email, find the relevant log entry to see whether the automation ran and what the result was.
• If a webhook to your system isn't receiving expected data, the log will show what Edvisor sent and what your endpoint returned.