Execution Audit

Workflow Run #10

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

Execution Metadata

Workflow
Morning Preparation
morning-preparation
Schedule
Manual / None
—
Started
2026-03-22 18:06:27 UTC
Finished
2026-03-22 18:06:59 UTC
Summary
Workflow completed successfully.
Step Timeline

Ordered Execution Trace

1
Schedule Next 1 Day
schedule-next-day
Succeeded
Started 2026-03-22 18:06:28 UTC
Finished 2026-03-22 18:06:29 UTC
Duration 1.2s
Summary
Schedule next day synced. Games upserted: 19.
2
Schedule Past Games Last 1 Day
schedule-past-day
Succeeded
Started 2026-03-22 18:06:29 UTC
Finished 2026-03-22 18:06:54 UTC
Duration 25.5s
Summary
Past-day schedule synced. Games upserted: 17.
4
Player Snapshots
player-snapshots
Succeeded
Started 2026-03-22 18:06:55 UTC
Finished 2026-03-22 18:06:58 UTC
Duration 3.2s
Summary
Player snapshots built. Rolling=591, Relevance=591, Batch=fb1ead34-24a6-4427-be8b-35e6d26e90cb, AsOf=2026-03-22 18:06:27Z.
5
ESPN Injuries
espn-injuries
Succeeded
Started 2026-03-22 18:06:58 UTC
Finished 2026-03-22 18:06:59 UTC
Duration 1.2s
Summary
ESPN injuries synced. Updated 128 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.