release_holdoutPermanently discard a project's reserved holdout window.
Area
Backtesting & Validation
Group
Holdout
Access
Write
Risk
Destructive
Details
Full description
Details
Discard a project's reserved holdout window (escape hatch). Clears holdout_start, holdout_end and resets holdout_validation_count. Permanent — a holdout window is allocated once, at project creation, and nothing re-allocates one after release, so the project is left with no reserved holdout at all.
Use this to recover when a backtest range falls entirely inside a stale reserved holdout (the run_backtest error points here).
Destructive — this throws away out-of-sample-integrity state (prior holdout validations no longer correspond to the reserved window), so it requires confirm=true. With confirm=false it is a no-op that just reports the current holdout window.
Args
project_id— project whose holdout window to release.confirm— must betrueto actually release.
release_holdout(project_id, confirm=true)
Capabilities
Bounded options and operating modes surfaced above the full JSON schema.
Required Inputs
project_idstringResearch project identifierOptional Inputs
confirmbooleanMust be true to actually release the holdout. This discards research-integrity state, so it is a no-op unless confirm=true.