Execution Audit

Workflow Run #35

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

Execution Metadata

Workflow
Morning Preparation
morning-preparation
Schedule
Manual / None
—
Started
2026-03-25 15:04:37 UTC
Finished
2026-03-25 15:05:30 UTC
Summary
Workflow completed successfully.
Step Timeline

Ordered Execution Trace

1
Schedule Next 1 Day
schedule-next-day
Succeeded
Started 2026-03-25 15:04:37 UTC
Finished 2026-03-25 15:04:44 UTC
Duration 7.3s
Summary
Schedule next day synced. Games upserted: 15.
2
Schedule Past Games Last 1 Day
schedule-past-day
Succeeded
Started 2026-03-25 15:04:45 UTC
Finished 2026-03-25 15:04:50 UTC
Duration 5.0s
Summary
Past-day schedule synced. Games upserted: 18.
4
Player Snapshots
player-snapshots
Succeeded
Started 2026-03-25 15:05:01 UTC
Finished 2026-03-25 15:05:24 UTC
Duration 23.0s
Summary
Player snapshots built. Rolling=594, Relevance=594, Batch=287c4f27-c3d0-43b4-8fab-87b482456450, AsOf=2026-03-25 15:04:37Z.
5
ESPN Injuries
espn-injuries
Succeeded
Started 2026-03-25 15:05:24 UTC
Finished 2026-03-25 15:05:30 UTC
Duration 6.3s
Summary
ESPN injuries synced. Updated 133 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.