Execution Audit

Workflow Run #8

Full execution trace, ordered step results, duration metrics, and failure context.
Back to Runs Dashboard
Status
Succeeded
Trigger
Manual
Duration
25.6s
Steps
4
Run Header

Execution Metadata

Workflow
Morning Preparation
morning-preparation
Schedule
Manual / None
—
Started
2026-03-22 05:07:30 UTC
Finished
2026-03-22 05:07:55 UTC
Summary
Workflow completed successfully.
Step Timeline

Ordered Execution Trace

1
Schedule Next 1 Day
schedule-next-day
Succeeded
Started 2026-03-22 05:07:30 UTC
Finished 2026-03-22 05:07:38 UTC
Duration 7.9s
Summary
Schedule next day synced. Games upserted: 17.
2
Schedule Past Games Last 1 Day
schedule-past-day
Succeeded
Started 2026-03-22 05:07:38 UTC
Finished 2026-03-22 05:07:38 UTC
Duration 646 ms
Summary
Past-day schedule synced. Games upserted: 16.
4
Player Snapshots
player-snapshots
Succeeded
Started 2026-03-22 05:07:50 UTC
Finished 2026-03-22 05:07:54 UTC
Duration 3.5s
Summary
Player snapshots built. Rolling=591, Relevance=591, Batch=582628b8-dd3f-4a4a-b8be-6a75c4f93c19, AsOf=2026-03-22 05:07:30Z.
5
ESPN Injuries
espn-injuries
Succeeded
Started 2026-03-22 05:07:54 UTC
Finished 2026-03-22 05:07:55 UTC
Duration 1.3s
Summary
ESPN injuries synced. Updated 122 player statuses.
Execution Summary

Step Status Breakdown

Succeeded 4
Failed 0
Running 0
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.