Skip to content

by Startups.Studio

Product Build and ship Issue Incident

Incident.acknowledge

POST /{namespace}/incidents/{incident}/acknowledge

Acknowledge records that an on-call Worker owns an open Incident and stops its escalation.

Noun: Incident
Mode: do
Event: Incident.acknowledged

You, to your agent

Acknowledge the latest incident.

curl -X POST https://api.sb/petpantry.shop/incidents/incident_1/acknowledge \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

import { $ } from 'startup-builder'

const incident = await $.Incident.acknowledge({ incident: 'incident_1' })

npx startup-builder do Incident.acknowledge --json '{"incident":"incident_1"}'

{
  "name": "do",
  "arguments": {
    "code": "return await $.Incident.acknowledge({ incident: 'incident_1' })"
  }
}

Inputs

Input	Type	Required	Description
`incident`	Incident	required	The open Incident.

Outputs

Output	Type	Required	Description
`incident`	Incident	required	The acknowledged Incident.

Effects

Emits Incident.acknowledged.
Performed by the Reliability Engineer.
Two-way: it runs at once, in the try, send and do modes.
Stops paging the next Worker in the rota.

Refuses when

Check	Error	Fix	Then call
The key is valid, but its scopes do not allow this operation.	`forbidden`	Use a key whose scopes cover the operation, or ask an owner of the namespace to grant them.	Incident.acknowledge

When it waits

Gate	Default
Decision class	Low: two-way, nothing at stake
Delay window	None: it runs once review passes.
Limit	The call Limit of the Permission it runs under.
Over the Limit	It waits `pending` for an Approval from the Founder. Approved, it runs; refused, it ends `refused` with `limit-exceeded`; unanswered by its deadline, it ends `canceled`.

Incident

Previous Page

Incident.create

Next Page