Skip to main content
DELETE
/
v1
/
investigation
/
{incidentId}
Abort investigation
curl --request DELETE \
  --url https://api.example.com/v1/investigation/{incidentId} \
  --header 'Authorization: <authorization>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "reason": "<string>"
}
'

Overview

Aborts an in-progress investigation for an incident. All running AI agents are stopped and any partial results are preserved. The incident status reverts to open so you can re-trigger investigation later if needed. Required role: admin
Aborting an investigation discards partial analysis. Any evidence already collected is preserved in triage, but AI findings are cleared. Re-triggering investigation starts fresh.

Request headers

Authorization
string
required
JWT Bearer token. Format: Bearer <your-jwt>.

Path parameters

incidentId
string
required
The incident whose investigation you want to abort. Example: inc_EXAMPLE_01JX.

Request body

reason
string
Optional reason for aborting. Recorded in the incident audit log.

Response

Returns 200 OK.
{
  "incidentId": "inc_EXAMPLE_01JX",
  "status": "open",
  "abortedAt": "2024-04-01T14:45:00Z",
  "agentsStopped": 3
}
FieldTypeDescription
incidentIdstringThe incident ID
statusstringReverted status — always open after abort
abortedAtstringISO 8601 timestamp of abort
agentsStoppedintegerNumber of running agents that were terminated

Error responses

StatusError codeDescription
401unauthorizedMissing or invalid JWT
403forbiddenCaller lacks admin role
404incident_not_foundNo incident with the given ID
409no_active_investigationNo investigation is currently running for this incident

Examples

curl https://api.causeflow.ai/v1/investigation/inc_EXAMPLE_01JX \
  -X DELETE \
  -H "Authorization: Bearer eyJhbGc..." \
  -H "Content-Type: application/json" \
  -d '{
    "reason": "False alarm — monitoring rule was misconfigured"
  }'

Start investigation

Re-trigger investigation after an abort

Update incident status

Manually close or resolve the incident