Timeouts

Tune timeout boundaries for scenario completion, cluster coordination, licensing, and correlation.

Runner Timeouts

WithScenarioCompletionTimeout controls graceful scenario shutdown duration. WithClusterCommandTimeout controls coordinator wait time for agent results.

Cross-Platform Correlation Timeout

CrossPlatformTrackingConfiguration.CorrelationTimeout controls source-destination match window (default 30s). TimeoutCountsAsFailure controls whether timeout increments failure totals.

Feature Usage Samples

How to use snippets for Timeouts.

Switch between C#, Java, Python, TypeScript, and JavaScript to see the native SDK shape for this sample.

Licensing note: every runnable sample requires a valid runner key via WithRunnerKey("...") or config key LoadStrike:RunnerKey.

Timeouts

var context = LoadStrikeRunner.RegisterScenarios(scenario)
    .WithScenarioCompletionTimeout(TimeSpan.FromSeconds(20))
    .WithClusterCommandTimeout(TimeSpan.FromSeconds(40))
    .WithRunnerKey("rkl_your_local_runner_key");

context.Run();

Cross-Platform Timeout

CorrelationTimeout

Defines how long LoadStrike will wait for a destination match before the tracked source event is treated as timed out.

ScenarioCompletionTimeout

Defines how long the runner waits for a scenario to shut down cleanly once execution has been asked to stop.

ClusterCommandTimeout

Defines how long a coordinator waits for agent-side results and cluster command acknowledgements.