What is Execution History?
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.
Why it matters:
✅ Verify automations are running correctly
✅ Troubleshoot failures fast
✅ See which clients triggered each automation
✅ Retry failed automations with one click
✅ Monitor performance over time
📍 How to Access Execution History
From Automations List
Find the automation you want to check
Click the three dots (⋮)
Select View History
📊 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
⚠️ 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
Examples:
New client added
Client entered Smart View
Form submitted
Days in Program milestone
Step-by-Step Breakdown
Click View steps to see:
Step name
Step status
Duration
Error details
Success confirmation
🔍 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.
📈 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
🎯 Execution Timing Logic
Instant triggers:
New Trainerize Client Added
Client Enters Stage
AI Form Submission
Every 6 hours:
Client Enters Smart View
At scheduled time:
Days in Program
Execution time:
Simple → 5–15 seconds
Medium → 15–30 seconds
Complex → 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
🎓 Real-World Scenarios
Scenario: Program Not Found
Fix wrong program name
Retry execution
Scenario: Client Didn’t Receive Welcome Message
Check Trainerize thread
Verify notifications
Automation ran correctly
Scenario: Milestone Didn’t Trigger
Missing program start date → add it
💡 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
How long is history kept?
90 days.
Can I delete execution history?
No.
Why isn’t my automation triggering?
Check filters, data, and activation toggle.
Why did my automation run twice?
User re-entered a Smart View or manual retry.
Can I pause automations?
Yes — toggle to Inactive.