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 with the event, status, actions, and duration.

If the automation hasn't run yet, you'll see a No executions yet message with a button to jump back to the configuration.

What's in a log entry

Each log entry includes:

• Timestamp — when the automation fired.
• Event — what triggered the run (for example, a specific Student Created event with the student details).
• Status — one of three:
• Actions and duration — each action that ran with its individual success or failure result, plus how long the whole execution took.

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

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.