Manage active sessions

Inspect a session before draining, terminating, or revoking it.

Before you start

Identify the session, affected agent or user, environment, and operational reason for the action.

Procedure

1. List sessions in the intended scope and inspect the target session’s state and route.

2. For maintenance, drain the affected path or session using the supported action so new admission stops and existing work has a bounded completion window.

3. For access removal, use revocation. For an immediate operational stop, use the supported termination action.

4. Inspect the resulting session state and administrative audit event.

Verify the result

Attempt the relevant follow-up request. Revoked, expired, or terminated state must not resume authorized execution after reconnect or recovery.

If it does not work

Drain and revocation have different purposes. If a caller must lose access, do not rely on a maintenance drain alone.

Read the related concept or consult the Admin API for exact request fields.

Implementation reference

Read the source contract.