Results

Run details distinguish failures that were recovered from failures that still need intervention. Recovered rows show the affected step and can link to the corresponding point in the run video when a recording is available. The Retrieve Run Results response includes:

was_recovered — whether at least one Maintenance Agent recovery succeeded
recovered_error_ids — the recovered error IDs, correlated with the response’s errors array

Lifecycle webhooks expose the same operational journey:

Event	Meaning
`execution.requeued`	The run is still in progress and waiting for another attempt (not a final status)
`execution.password_updated`	Password rotation succeeded and the credential was updated
`agent.decision_requested`	The recovery agent asked a human to make a decision
`agent.decision_answered`	That decision was answered, declined, expired, cancelled or failed
`agent.decision_applied`	The recovery agent applied a remembered, admin-approved answer instead of asking
`execution.failed`	The run is final and will not be retried

Eligible organizations may also receive a monthly recap summarizing recovered popup blockers, selector failures, outages, slow-loading pages, and password updates. Delivery depends on organization eligibility and a minimum of 10 recoveries in the month.

Getting Started

Concepts

API Reference

SDK

Integrations