Execution Audit
Workflow Run #168
Full execution trace, ordered step results, duration metrics, and failure context.
Status
Running
Trigger
Manual
Duration
—
Steps
7
Run Header
Execution Metadata
Step Timeline
Ordered Execution Trace
1
Schedule Next 1 Day
schedule-next-day
Summary
Schedule next day synced. Games upserted: 1.
2
Completed Game Final Boxscore Sync
schedule-past-day
Summary
Past-day schedule and completed-game final boxscore sync finished. Games upserted: 1. Completed games synced: 0.
3
Player Snapshots
player-snapshots
Summary
Player snapshots built. Rolling=541, Relevance=532, Batch=7c9b1bbb-b0d3-49b0-af9f-729e4cda42ba, AsOf=2026-05-29 15:00:22Z.
4
ESPN Injuries
espn-injuries
Summary
ESPN injuries synced. Updated 125 player statuses.
5
Team Stats Snapshot
team-stats-snapshot
Summary
Team stats snapshot skipped. Suspicious team stats batch detected: all 30 comparable rows are identical to the latest existing batch for LastNGames=10. Sync aborted.
6
Daily Playoff Win Probability Snapshot
daily-playoff-win-probability-snapshot
Summary
Daily playoff win-probability snapshot built for 2026-05-29. RunId=52.
7
Historical Availability Daily States
historical-availability-daily-states
Execution Summary
Step Status Breakdown
Succeeded
6
Failed
0
Running
1
Skipped
0
Partial
0
Operator Notes
Reading This Run
Use the ordered timeline to identify the exact failure boundary.
Compare workflow summary vs step summary to isolate whether failure was orchestration-level or step-level.
Long durations usually indicate remote source latency or backfill-heavy sync execution.