Execution Audit

Workflow Run #6

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

Execution Metadata

Workflow
Morning Preparation
morning-preparation
Schedule
Manual / None
—
Started
2026-03-20 17:36:18 UTC
Finished
2026-03-20 17:36:48 UTC
Summary
Workflow completed successfully.
Step Timeline

Ordered Execution Trace

1
Schedule Next 1 Day
schedule-next-day
Succeeded
Started 2026-03-20 17:36:18 UTC
Finished 2026-03-20 17:36:19 UTC
Duration 1.1s
Summary
Schedule next day synced. Games upserted: 16.
2
Schedule Past Games Last 1 Day
schedule-past-day
Succeeded
Started 2026-03-20 17:36:19 UTC
Finished 2026-03-20 17:36:34 UTC
Duration 15.2s
Summary
Past-day schedule synced. Games upserted: 14.
4
Player Snapshots
player-snapshots
Succeeded
Started 2026-03-20 17:36:44 UTC
Finished 2026-03-20 17:36:47 UTC
Duration 3.1s
Summary
Player snapshots built. Rolling=590, Relevance=590, Batch=32a8722f-7817-4160-a655-b0ed66fa70c5, AsOf=2026-03-20 17:36:18Z.
5
ESPN Injuries
espn-injuries
Succeeded
Started 2026-03-20 17:36:47 UTC
Finished 2026-03-20 17:36:48 UTC
Duration 1.2s
Summary
ESPN injuries synced. Updated 127 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.