# incident.degraded

It worked, but worse than it should: a fallback, a retry, a slow dependency

Profile: [Logs](https://www.prongs.dev/docs/intents/logs.md) · Written with: [`log()`](https://www.prongs.dev/docs/profiles/logs.md) · Level: `warn`

## Example

```ts
log('incident.degraded', 'Search fell back to the cached index', { tookMs: 4200 });
```

Writes

```ts
{
  "intent": "incident.degraded",
  "level": "warn",
  "alert": false,
  "message": "Search fell back to the cached index",
  "data": {
    "tookMs": 4200
  },
  "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 for… | Use |
|---|---|
| It worked, but worse than it should: a fallback, a retry, a slow dependency | `incident.degraded` (this page) |
| Something that recovered or fell back (rather than [`incident.failed`](https://www.prongs.dev/docs/intents/incident/failed.md)) | `incident.degraded` (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.

- Built from: [`level.warn`](https://www.prongs.dev/docs/intents/logs.md#level-warn)
- Written by: [`failure.upstream`](https://www.prongs.dev/docs/intents/failure/upstream.md)

## For registry authors

**Starter intents.** These are the intents `prongs add logs` puts in your registry. Change levels through the [`level.*`](https://www.prongs.dev/docs/intents/logs.md#level) intents, and point [`log()`](https://www.prongs.dev/docs/profiles/logs.md) at your logger.

The entry `prongs add logs` writes into your registry. Change the level through its [`level.*`](https://www.prongs.dev/docs/intents/logs.md#level) ref.

```ts
'incident.degraded': {
  kind: 'semantic',
  description: 'It worked, but worse than it should: a fallback, a retry, a slow dependency',
  refs: ['level.warn'],
},
```
