Revalidate after changes
Disablement
For Sandbox/model connections, disabling blocks new Sessions and new Runs on existing Sessions. The worker checks again before a new Harness invocation, including work queued before disablement. An identical already-accepted idempotency request can still return its original Run. Existing invocation recovery and resource cleanup remain necessary.Roll out a configuration change
Separate credential repair from changing the execution environment. After a credential change, validation and enablement restore eligibility, but do not prove that an existing cloud resource is accessible under the new credential. Keep enough private resource evidence to investigate account or permission mismatches. Changing a connection’s account is not a resource migration. For a planned environment change, identify dependent Sessions, settle their active work, prepare and verify the intended connection, then create a canary Session with the desired definition. Run the actual required task and cleanup checks before directing new work to it. Existing Sessions retain their pinned execution configuration; a new validation result does not rewrite that snapshot.Close dependencies before deletion
Inspect dependent Sessions, settle active Runs, close each, and confirm cleanup. Deletion with remaining dependencies returnsconnection_in_use. Reconcile unknown deletions rather than removing database records to hide dependencies.
Then use delete_connection / deleteConnection. This deletes the Hexagon connection, not the upstream account or its API key. Upstream revocation requires the corresponding Provider management action.