Execution History is your automation monitoring dashboard. It shows every time an automation has run, whether it succeeded or failed, and full details for each step.
How to Access Execution History
From Automations List
Go to Automations
Find the automation you want to check
Click the three dots (⋮)
Select View History
From a Client's Dashboard
Go to Trainerize Clients and open a client
Click the Automations tab in the left sidebar
This shows the 50 most recent executions for that specific client
Execution Status Types
Completed
Automation ran successfully
All actions executed
Nothing to fix
Failed
Automation encountered an error
How to fix:
Expand the execution
Read the error
Fix the issue
Click Retry
Common causes: Missing required data, program not found, no active message thread, deleted client, API error.
Running
Currently processing actions
Normally 5–30 seconds
If stuck > 5 minutes, contact support
Pending
Queued and waiting to run
Usually only a few seconds
Skipped
Trigger conditions were not met (e.g., tag filter didn't match)
Send Message dedupe: if the automation already sent this exact message to this client earlier in the same day (UTC), subsequent runs mark the Send Message step as skipped so clients never receive duplicate messages. Other steps (tag add, stage move, etc.) still run normally.
No action needed
Cancelled
Cancelled manually or due to system maintenance
What Each Execution Shows
Header
Automation name
Status badge
Timestamp
Client name (clickable)
Duration
Progress bar "X/Y steps"
Trigger Details
Shows what triggered the automation (e.g., new client added, form submitted, tag added, client deactivated).
Step-by-Step Breakdown
Click View steps to see:
Step name and action type
Step status (success, failed, or skipped)
Duration per step
Error details if the step failed
Result message if successful
Searching & Filtering
Search Bar
Search by:
Client name
Automation name
Trigger type
Status Filter
All
Success
Failed
Running
Cancelled
Pro Tip: Start with Failed to find issues instantly.
Retrying Failed Automations
How to Retry:
Open execution history
Click Retry
The automation runs again immediately
Retry when:
Temporary network error
API error
You fixed missing data
Do NOT retry when:
Client no longer exists
Program/template doesn't exist
Automation setup needs changing
Common Errors & Fixes
"Client not found in Trainerize"
Client deleted — remove/update client.
"No active thread"
Assign coach or ensure Trainerize messaging is active.
"Program not found"
Program name mismatch — select valid program.
"Template not found"
AI Check-In template deleted — update automation.
"Missing required field: email"
Update client profile with missing data.
"Timeout / API error"
Retry after a few minutes.
"Rate limit exceeded"
Too many requests — retry later.
Execution Timing Logic
Instant triggers (fire immediately when the event happens):
New Trainerize Client Added
Client Reactivated
Client Deactivated
Client Enters Stage
AI Form Submission
Trainerize Tag Added
Trainerize Tag Removed
AI Task Created
Checked every few minutes:
Client Enters Smart View
At scheduled time:
Days in Program
Execution time per automation:
Simple (1–2 actions) — 5–15 seconds
Medium (3–5 actions) — 15–30 seconds
Complex (6+ actions) — 30–60 seconds
Reading the Progress Bar
Full Green: All steps completed
Partial Red: Failed mid-way
Blue: Running
Gray: Pending / Cancelled
What Gets Logged
Logged:
Trigger details
Client name
Execution timestamps
Action statuses
Errors
Durations
Not Logged:
Message content
Full form responses
Sensitive fields
Monitoring Best Practices
Check Execution History weekly
Filter by Failed first
Monitor new automations daily for the first week
Compare successful vs failed executions
Fix issues before retrying
Pro Tips
Always test new automations using Test Mode
Add Slack alerts via webhooks for important automations
Document recurring errors
Compare successful vs failed runs when diagnosing issues
Check execution ID when contacting support
Frequently Asked Questions
Can I delete execution history?
No. Execution history is retained automatically.
Why isn't my automation triggering?
Check filters, data, and activation toggle.
Why did my automation run twice?
This can happen when a client re-enters a Smart View, a Trainerize webhook is delivered twice, a reactivation event overlaps with a new-client event, or you manually retry. Don't worry — we automatically dedupe the Send Message step so clients won't receive duplicate messages. If you see two executions in the history, check the step details: the second run will show the Send Message step as "skipped" while still running other actions normally.
Can I pause automations?
Yes — toggle to Inactive.