Monitoring automation runs

Last updated: July 24, 2026

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, 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.

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 (for example, "Proposal created").
  • 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.

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