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();
import com.loadstrike.runtime.LoadStrikeRuntime.LoadStrikeRunner;
LoadStrikeRunner
.registerScenarios(scenario)
.withScenarioCompletionTimeout(20d)
.withClusterCommandTimeout(40d)
.withRunnerKey("rkl_your_local_runner_key")
.run();
from loadstrike_sdk import LoadStrikeRunner
LoadStrikeRunner.register_scenarios(scenario) \
.with_scenario_completion_timeout(20) \
.with_cluster_command_timeout(40) \
.with_runner_key("rkl_your_local_runner_key") \
.run()
import { LoadStrikeRunner } from "@loadstrike/loadstrike-sdk";
await LoadStrikeRunner
.registerScenarios(scenario)
.withScenarioCompletionTimeout(20)
.withClusterCommandTimeout(40)
.withRunnerKey("rkl_your_local_runner_key")
.run();
const { LoadStrikeRunner } = require("@loadstrike/loadstrike-sdk");
await LoadStrikeRunner
.registerScenarios(scenario)
.withScenarioCompletionTimeout(20)
.withClusterCommandTimeout(40)
.withRunnerKey("rkl_your_local_runner_key")
.run();
Cross-Platform Timeout
Defines how long LoadStrike will wait for a destination match before the tracked source event is treated as timed out.
Defines how long the runner waits for a scenario to shut down cleanly once execution has been asked to stop.
Defines how long a coordinator waits for agent-side results and cluster command acknowledgements.