Reading your dashboard
Your dashboard is where you see what your automations are doing. This page teaches you how to read it, what the numbers mean, and when to take action.
Understanding runs
Every time an automation executes, that’s a “run.” If your lead response workflow fires 15 times today, that’s 15 runs. Each run is logged with a timestamp, the data it processed, and the result.
Run statuses
Each run has one of four statuses:
- Triggered - the automation detected its trigger condition. It’s about to start.
- Running - the workflow is actively executing its steps.
- Completed - everything finished successfully. The output was delivered.
- Failed - something went wrong. The run stopped before completing.
A healthy automation shows almost all “completed” statuses. The occasional failure is normal - an API timeout, a malformed input, a temporary outage. Repeated failures are not normal and need attention.
Reading run history
Your run history shows a chronological list of every execution. For each run, you can see:
- What triggered it - the event or schedule that started the run
- When it ran - timestamp down to the minute
- What it did - each step the automation executed, in order
- The result - what was produced, sent, or updated
Click into any individual run to see the full detail. This is especially useful when troubleshooting.
Understanding logs
When a run fails, the log tells you why. Common failure reasons include:
- A connected service was temporarily unavailable
- The input data was missing a required field
- A rate limit was hit (too many requests too fast)
- Authentication expired and needs to be refreshed
You don’t need to fix these yourself. But understanding what the log says helps you communicate the issue clearly and get it resolved faster.
Analytics to watch
Your dashboard surfaces key metrics:
- Success rate - percentage of runs that complete without errors. Aim for 95%+.
- Volume trends - are your automations running more or less over time? Growth usually means they’re working.
- Time savings - estimated hours saved based on run count and average manual time per task.
When to flag something
Reach out to your Advizr team when you see:
- The same automation failing multiple times in a row
- Success rate dropping below 90%
- Results that look wrong or unexpected
- A sudden spike or drop in run volume you can’t explain
Catching these early prevents small issues from becoming big problems.
Check your understanding
Triggered (the automation detected its trigger condition), running (actively executing), completed (finished successfully), and failed (stopped before completing).
Aim for 95% or higher. The occasional failure is normal - an API timeout or malformed input - but repeated failures are not and need attention.
When the same automation fails multiple times in a row, success rate drops below 90%, results look wrong or unexpected, or there is a sudden spike or drop in run volume you cannot explain.
Next steps
Once you’re comfortable reading your dashboard, learn how to improve your workflows in Optimizing Workflows.