Execution Audit
Workflow Run #34
Full execution trace, ordered step results, duration metrics, and failure context.
Status
Failed
Trigger
Manual
Duration
27m 49s
Steps
6
Run Header
Execution Metadata
Summary
Workflow failed at step 'Run Validation'.
Error
System.InvalidOperationException: Baseline and challenger model version ids must be different. at BettingOdds.App.Projections.Services.Validation.ProjectionValidationWindowBuilder.ValidateRequest(ProjectionValidationCreateRequest request) in C:\Users\Cesar\Documents\bettingodds2\BettingOdds\App\Projections\Services\Optimization\Validation\ProjectionValidationWindowBuilder.cs:line 91 at BettingOdds.App.Projections.Services.Validation.ProjectionValidationWindowBuilder.BuildWindows(ProjectionValidationCreateRequest request) in C:\Users\Cesar\Documents\bettingodds2\BettingOdds\App\Projections\Services\Optimization\Validation\ProjectionValidationWindowBuilder.cs:line 14 at BettingOdds.App.Projections.Services.Validation.ProjectionValidationService.CreateValidationRunAsync(ProjectionValidationCreateRequest request, CancellationToken ct) in C:\Users\Cesar\Documents\bettingodds2\BettingOdds\App\Projections\Services\Optimization\Validation\ProjectionValidationService.cs:line 38 at BettingOdds.App.Automation.Steps.CampaignExperiments.OptimizationCampaignValidationStepExecutor.ExecuteAsync(AutomationExecutionContext context, CancellationToken ct) in C:\Users\Cesar\Documents\bettingodds2\BettingOdds\App\Automation\Steps\CampaignExperiments\OptimizationCampaignValidationStepExecutor.cs:line 147 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
Summary
Selected optimization campaign 'Minutes Calibration Sprint 01' (minutes-calibration-sprint-01).
2
Bootstrap Campaign Run
optimization-campaign-bootstrap
Summary
Bootstrapped campaign run 7 for 'Minutes Calibration Sprint 01'. Baseline model version = 45. Search anchor model version = 45.
3
Create Experiment
optimization-campaign-create-experiment
Summary
Created experiment 16 for campaign 'Minutes Calibration Sprint 01'.
4
Run Experiment
optimization-campaign-run-experiment
Summary
Experiment 16 already completed. Skipping rerun.
5
Evaluate Results
optimization-campaign-evaluate
Summary
Winner: Model 45 | Improvement: 0
6
Run Validation
optimization-campaign-validation
Error
System.InvalidOperationException: Baseline and challenger model version ids must be different. at BettingOdds.App.Projections.Services.Validation.ProjectionValidationWindowBuilder.ValidateRequest(ProjectionValidationCreateRequest request) in C:\Users\Cesar\Documents\bettingodds2\BettingOdds\App\Projections\Services\Optimization\Validation\ProjectionValidationWindowBuilder.cs:line 91 at BettingOdds.App.Projections.Services.Validation.ProjectionValidationWindowBuilder.BuildWindows(ProjectionValidationCreateRequest request) in C:\Users\Cesar\Documents\bettingodds2\BettingOdds\App\Projections\Services\Optimization\Validation\ProjectionValidationWindowBuilder.cs:line 14 at BettingOdds.App.Projections.Services.Validation.ProjectionValidationService.CreateValidationRunAsync(ProjectionValidationCreateRequest request, CancellationToken ct) in C:\Users\Cesar\Documents\bettingodds2\BettingOdds\App\Projections\Services\Optimization\Validation\ProjectionValidationService.cs:line 38 at BettingOdds.App.Automation.Steps.CampaignExperiments.OptimizationCampaignValidationStepExecutor.ExecuteAsync(AutomationExecutionContext context, CancellationToken ct) in C:\Users\Cesar\Documents\bettingodds2\BettingOdds\App\Automation\Steps\CampaignExperiments\OptimizationCampaignValidationStepExecutor.cs:line 147 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
5
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.