Run recovery for a single failed resource

Clears a specific failed resource's failure state so the simulation engine restores it to healthy over subsequent steps. Deactivates any in-effect reversible failure injection targeting the resource (instance_down, database_overload), restores snapshotted characteristics where available, and resets the resource's health counters to zero so only subsequent qualifying simulation steps count.

Returns 409 PERMANENT_DATA_LOSS for destroyed data that has not been explicitly rebuilt. Generic recovery never clears dataState; an empty rebuilt database can serve again while its original data remains lost.

The quick inject-failure endpoint is intentionally different: its positive failureParkSteps window is automatic, so the node may rejoin routing after the window without this endpoint. Use recover-resource when an explicit recovery is required for a persistent reversible instance_down failure; poll isRoutable, routedRps, and recoveryProgress after either flow.

instance_kill cannot be recovered — that failure type permanently removes the target resource from the simulation. Calling this endpoint with the killed resource's id returns 400 RESOURCE_KILLED; re-add the resource via PATCH /simulations/{simulationId}, or prefer instance_down when you want a reversible outage.

Scoped to the targeted resource only — other resources that remain failed are not affected.

The response echoes the applied outcome, including stepsToHealthy: a lower-bound estimate of the POST /step (or step-hybrid) calls needed for the engine to demote the resource back to healthy under the current recovery policy (defaults: critical→warning after 4 steps below 80% CPU, warning→healthy after 3 steps below 70%; the default lower bound is 7 steps from critical). stepsToHealthyIsLowerBound is always true: explicitly failed resources may require an additional failure-park transition before cooldown resumes, and a CPU threshold breach resets the cooldown counter. Callers should take at least stepsToHealthy steps, then poll GET /simulations/{simulationId} until the resource is healthy.

Works for every provider (AWS, GCP, Azure, OCI, DigitalOcean) — unlike bulk-resize, which is DigitalOcean-only.

Provide resourceName or resourceId. Returns 400 when the resource cannot be found, was permanently removed by instance_kill, or is already healthy.

Requires write scope and ownership.