# A schedule's fire history

GET

/v1/schedules/{triggerId}/fires

```sh
curl --request GET \
  --url 'https://example.com/v1/schedules/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/fires?limit=25' \
  --header 'Authorization: Bearer <token>'
```

Newest first: each occurrence (and `run-now`) the schedule fired for, and what came of it: the run it started, or why it was skipped, refused or failed.

## Authorizations

- **[bearerAuth](https://docs.kindgi.com/v0.1.10/reference/api.md#bearerauth)**

## Parameters

### Path Parameters

**triggerId**

required

string format: uuid

TriggerId — the trigger id (a UUID).

### Query Parameters

**limit**

integer

default: 25 >= 1 <= 100

1..100. Default 25.

**cursor**

string

Where the previous page ended: its `nextCursor`, as it came. A runtime that seals cursors takes one only for the same list, filters and caller, within a day; otherwise `400 bad-input`, and the list starts again without it. Absent → first page.

## Responses

### 200

Page of fires.

application/json

object

**data**

required

Array\<object>

One fire of a schedule (an occurrence, or a `run-now`) and what came of it. `pending` while its run is being started.

object

**fireId**

required

string

**scheduleId**

required

string

**triggerId**

required

string

**scheduledFor**

The occurrence it is for; absent on a `run-now` fire.

string format: date-time

**firedAt**

required

string format: date-time

**outcome**

required

`skipped-overlap`: the previous fire’s run was still going (`overlap: skip`). `skipped-erasure`: the person the fire acts for is being erased, so no new run starts for them until the erasure completes. `skipped`, as `detail` says: what an improve schedule waits for wasn’t there (its threshold, or its monthly cap); the target’s project is suspended (`project-suspended`), so no run or pass started; its run or pass hadn’t started when its tenant was suspended, and the restore concluded it (`tenant-suspended`); or its tenant was suspended or closing as its run started (`tenant-suspended`, `tenant-closing`). None of the skipped outcomes counts toward the auto-pause; `refused` and `failed` do, unless `countsTowardPause` is `false`. A skip for a suspension or a close (`project-suspended`, `tenant-suspended`, `tenant-closing`) doesn’t reset the auto-pause’s count of fires in a row either.

string

Allowed values: pending started skipped-overlap skipped-erasure skipped refused failed

**runId**

The run it started.

string format: uuid

**passId**

The improvement pass it started (an improve schedule).

string format: uuid

**detail**

Why it was refused, skipped or failed.

string

**countsTowardPause**

Whether this fire counted toward the trigger’s auto-pause (5 in a row by default). `false` for a refusal for a limit, such as the tenant’s runs pending (`detail` starts `rate-limited:`): the limit passes, and the trigger isn’t at fault. Absent from a runtime that doesn’t say: `refused` and `failed` fires counted, and the others didn’t.

boolean

**missedCount**

Occurrences this fire stood in for after a gap (`catchUp: latest`).

integer

\>= 1

**manual**

A `run-now` fire, outside the schedule.

boolean

**hasMore**

required

boolean

**nextCursor**

string

##### Example

```json
{
  "data": [
    {
      "outcome": "pending"
    }
  ]
}
```

### 401

Missing / malformed / expired / revoked bearer token.

application/json

object

**error**

required

object

**code**

required

Stable machine-readable discriminant. Values match domain error codes (see `docs/API-ROUTE-CONVENTIONS.md` §4.3).

string

**message**

required

string

**details**

Optional, kind-specific.

object

**_key_**

additional properties

any

**requestId**

required

Server-assigned request id; also echoed via `X-Request-Id` header.

string

##### Examplegenerated

```json
{
  "error": {
    "code": "example",
    "message": "example",
    "details": {},
    "requestId": "example"
  }
}
```

### 404

No cron trigger with that id.

application/json

object

**error**

required

object

**code**

required

Stable machine-readable discriminant. Values match domain error codes (see `docs/API-ROUTE-CONVENTIONS.md` §4.3).

string

**message**

required

string

**details**

Optional, kind-specific.

object

**_key_**

additional properties

any

**requestId**

required

Server-assigned request id; also echoed via `X-Request-Id` header.

string

##### Examplegenerated

```json
{
  "error": {
    "code": "example",
    "message": "example",
    "details": {},
    "requestId": "example"
  }
}
```

### 501

`trigger-operation-unsupported`: this deployment keeps no fire history.

application/json

object

**error**

required

object

**code**

required

Stable machine-readable discriminant. Values match domain error codes (see `docs/API-ROUTE-CONVENTIONS.md` §4.3).

string

**message**

required

string

**details**

Optional, kind-specific.

object

**_key_**

additional properties

any

**requestId**

required

Server-assigned request id; also echoed via `X-Request-Id` header.

string

##### Examplegenerated

```json
{
  "error": {
    "code": "example",
    "message": "example",
    "details": {},
    "requestId": "example"
  }
}
```

## See also

- [`GET /v1/schedules/{triggerId}`: Fetch a cron schedule](https://docs.kindgi.com/v0.1.10/reference/api/operations/schedulesget.md)
- [`PATCH /v1/schedules/{triggerId}`: Update a cron schedule](https://docs.kindgi.com/v0.1.10/reference/api/operations/schedulesupdate.md)
- [`POST /v1/schedules/{triggerId}/pause`: Pause a cron schedule](https://docs.kindgi.com/v0.1.10/reference/api/operations/schedulespause.md)
- [`POST /v1/schedules/{triggerId}/resume`: Resume a cron schedule](https://docs.kindgi.com/v0.1.10/reference/api/operations/schedulesresume.md)
- [Error code `trigger-operation-unsupported`](https://docs.kindgi.com/v0.1.10/reference/errors.md#trigger-operation-unsupported)
- [Every error code](https://docs.kindgi.com/v0.1.10/reference/errors.md)