Execution Audit

Workflow Run #30

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

Execution Metadata

Workflow
Optimization Campaign
optimization-campaign
Schedule
Manual / None
—
Started
2026-03-24 19:38:29 UTC
Finished
2026-03-24 19:38:30 UTC
Summary
Workflow failed at step 'Bootstrap Campaign Run'.
Error
System.InvalidOperationException: Campaign 'Minutes Calibration Sprint 01' reached MaxRuns (3). No further runs allowed.
   at BettingOdds.App.Automation.CampaignExperiments.ProjectionOptimizationCampaignRunBootstrapService.BootstrapRunAsync(Int32 projectionOptimizationCampaignId, String startedBy, CancellationToken ct) in C:\Users\Cesar\Documents\bettingodds2\BettingOdds\App\Automation\CampaignExperiments\ProjectionOptimizationCampaignRunBootstrapService.cs:line 85
   at BettingOdds.App.Automation.Steps.CampaignExperiments.OptimizationCampaignBootstrapStepExecutor.ExecuteAsync(AutomationExecutionContext context, CancellationToken ct) in C:\Users\Cesar\Documents\bettingodds2\BettingOdds\App\Automation\Steps\CampaignExperiments\OptimizationCampaignBootstrapStepExecutor.cs:line 41
   at BettingOdds.App.Automation.Services.AutomationWorkflowRunner.RunManualAsync(AutomationManualRunRequest request, CancellationToken ct) in C:\Users\Cesar\Documents\bettingodds2\BettingOdds\App\Automation\Services\AutomationWorkflowRunner.cs:line 136
Step Timeline

Ordered Execution Trace

1
Select Campaign
optimization-campaign-select
Succeeded
Started 2026-03-24 19:38:29 UTC
Finished 2026-03-24 19:38:29 UTC
Duration 629 ms
Summary
Selected optimization campaign 'Minutes Calibration Sprint 01' (minutes-calibration-sprint-01).
2
Bootstrap Campaign Run
optimization-campaign-bootstrap
Failed
Started 2026-03-24 19:38:29 UTC
Finished 2026-03-24 19:38:30 UTC
Duration 611 ms
Error
System.InvalidOperationException: Campaign 'Minutes Calibration Sprint 01' reached MaxRuns (3). No further runs allowed.
   at BettingOdds.App.Automation.CampaignExperiments.ProjectionOptimizationCampaignRunBootstrapService.BootstrapRunAsync(Int32 projectionOptimizationCampaignId, String startedBy, CancellationToken ct) in C:\Users\Cesar\Documents\bettingodds2\BettingOdds\App\Automation\CampaignExperiments\ProjectionOptimizationCampaignRunBootstrapService.cs:line 85
   at BettingOdds.App.Automation.Steps.CampaignExperiments.OptimizationCampaignBootstrapStepExecutor.ExecuteAsync(AutomationExecutionContext context, CancellationToken ct) in C:\Users\Cesar\Documents\bettingodds2\BettingOdds\App\Automation\Steps\CampaignExperiments\OptimizationCampaignBootstrapStepExecutor.cs:line 41
   at BettingOdds.App.Automation.Services.AutomationWorkflowRunner.RunManualAsync(AutomationManualRunRequest request, CancellationToken ct) in C:\Users\Cesar\Documents\bettingodds2\BettingOdds\App\Automation\Services\AutomationWorkflowRunner.cs:line 136
Execution Summary

Step Status Breakdown

Succeeded 1
Failed 1
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.