GitHub

incident.failed

Something broke and someone should look: a request, a job, a dependency

Profile

Logs

Written with

log()

Level

error

Alerts

yes
View as Markdown

Incident intents

Example

TS
log('incident.failed', 'Feed refresh stopped', { source: 'npr', attempt: 3 });
Writes
TS
{
  "intent": "incident.failed",
  "level": "error",
  "alert": true,
  "message": "Feed refresh stopped",
  "data": {
    "source": "npr",
    "attempt": 3
  },
  "time": "2026-10-09T12:00:00.000Z"
}

Choosing between neighbours

Find the row that describes your case, and use the intent on the right.

  • If it is

    Use

  • Something broke and someone should look: a request, a job, a dependency

    incident.failed this page

  • Something that recovered or fell back

    incident.degraded

  • A job that stopped on an error

    rather than job.finished
    incident.failed this page

Connections

Declared in the registry, both directions. Where an intent is used in your own code is something check and the gallery see; this site has no app code.

For registry authors

Starter intents. These are the intents prongs add logs puts in your registry. Change levels through the level.* intents, and point log() at your logger.

The entry prongs add logs writes into your registry. Change the level through its level.* ref.

TS
'incident.failed': {
  kind: 'semantic',
  description: 'Something broke and someone should look: a request, a job, a dependency',
  refs: ['level.error'],
  binding: { alert: true },
  notFor: [
    {
      context: 'something that recovered or fell back',
      instead: 'incident.degraded',
    },
    {
      context: 'a caller’s own mistake, like invalid input: return a request.* error and do not log it as an incident',
    },
  ],
},