Force-kill a stuck session (SIGKILL its wedged engine, then tear it down)
POST/api/sessions/:sessionId/force-kill
Force-kill a stuck session (SIGKILL its wedged engine, then tear it down)
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 502
- 503
Session force-killed
Session is not started
The API key is missing, unknown, revoked, or expired
The API key's role, session or chat scope, or IP allow-list does not allow this operation
Session not found
Session was stopped locally, but the engine force-kill did not complete (the force-destroy threw or timed out, so the engine process may still be running). The body carries code: 'SESSION_FORCE_KILL_INCOMPLETE'; the status is settled to disconnected and no success audit is written. Restart the node to reap a leaked process.
The database did not answer the read of the session, so nothing was killed. Retry the force-kill.