Execution Audit

Workflow Run #22

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

Execution Metadata

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

Ordered Execution Trace

1
Schedule Next 1 Day
schedule-next-day
Succeeded
Started 2026-03-24 15:00:16 UTC
Finished 2026-03-24 15:00:22 UTC
Duration 6.8s
Summary
Schedule next day synced. Games upserted: 18.
2
Schedule Past Games Last 1 Day
schedule-past-day
Succeeded
Started 2026-03-24 15:00:22 UTC
Finished 2026-03-24 15:00:28 UTC
Duration 5.5s
Summary
Past-day schedule synced. Games upserted: 18.
4
Player Snapshots
player-snapshots
Succeeded
Started 2026-03-24 15:00:57 UTC
Finished 2026-03-24 15:01:19 UTC
Duration 22.7s
Summary
Player snapshots built. Rolling=594, Relevance=594, Batch=9a30b071-c718-4af6-b399-5d3aceccfda1, AsOf=2026-03-24 15:00:15Z.
5
ESPN Injuries
espn-injuries
Succeeded
Started 2026-03-24 15:01:19 UTC
Finished 2026-03-24 15:01:26 UTC
Duration 6.3s
Summary
ESPN injuries synced. Updated 124 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.