Execution Audit

Workflow Run #39

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

Execution Metadata

Workflow
Morning Preparation
morning-preparation
Schedule
Manual / None
—
Started
2026-03-26 15:00:06 UTC
Finished
2026-03-26 15:00:26 UTC
Summary
Workflow completed successfully.
Step Timeline

Ordered Execution Trace

1
Schedule Next 1 Day
schedule-next-day
Succeeded
Started 2026-03-26 15:00:06 UTC
Finished 2026-03-26 15:00:07 UTC
Duration 1.1s
Summary
Schedule next day synced. Games upserted: 13.
2
Schedule Past Games Last 1 Day
schedule-past-day
Succeeded
Started 2026-03-26 15:00:07 UTC
Finished 2026-03-26 15:00:08 UTC
Duration 735 ms
Summary
Past-day schedule synced. Games upserted: 15.
4
Player Snapshots
player-snapshots
Succeeded
Started 2026-03-26 15:00:21 UTC
Finished 2026-03-26 15:00:25 UTC
Duration 3.6s
Summary
Player snapshots built. Rolling=594, Relevance=532, Batch=f89f345c-5a3f-4d38-a3ac-adec0e4eb001, AsOf=2026-03-26 15:00:06Z.
5
ESPN Injuries
espn-injuries
Succeeded
Started 2026-03-26 15:00:25 UTC
Finished 2026-03-26 15:00:26 UTC
Duration 1.1s
Summary
ESPN injuries synced. Updated 120 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.