Skip to main content

# kater job history

Lists a deployment's job runs, newest first, with each run's state and times.

{/* Written by apps/landing-page/scripts/docs/write_cli_reference.py from the kater CLI's own help and scripts/docs/cli-reference.md. Do not edit it by hand: change those, then run the script. */}

Use it to check that the scheduled runs happen, and to find a run's id for `kater logs job`.

## Examples

```bash
# List the production deployment's latest runs
kater job history --kater-root . --deployment production
# List the last 5 runs of the sync_snowflake job
kater job history --kater-root . --deployment production --job sync_snowflake --limit 5
```

## Options

<div class="cli-options">

| Option | Description |
| --- | --- |
| `--deployment <name>` | Required. The deployment whose runs to list, such as `production`. |
| `--job <name>` | Lists only this job's runs, by its name, such as `sync_snowflake`. |
| `--limit <n>` | The most runs to list, from 1 to 1000. The default is `20`. |

</div>

It also takes the [global options](https://kater.ai/docs/cli-reference/global-options/) `--json`, `--kater-root`, `--scope` and `--help`.

## What each run gives

Its `id`, `job` and `connection`, and what started it (`trigger`): `scheduled`, `manual` or `after`. Then its `status`, and when it was due, queued, started and finished. A run's status is `queued`, `running`, `succeeded`, `failed`, `interrupted` or `cancelled`.

## See also

- [`kater job`](https://kater.ai/docs/cli-reference/job/)
- [All commands](https://kater.ai/docs/cli-reference/kater/)

On this page

Examples
Options
What each run gives
See also

Kater CLI Run Kater's services job

kater job history

Lists a deployment's job runs, newest first, with each run's state and times.

Use it to check that the scheduled runs happen, and to find a run’s id for kater logs job.

Examples

# List the production deployment's latest runs
kater job history --kater-root . --deployment production
# List the last 5 runs of the sync_snowflake job
kater job history --kater-root . --deployment production --job sync_snowflake --limit 5

Options

Option	Description
`--deployment <name>`	Required. The deployment whose runs to list, such as `production`.
`--job <name>`	Lists only this job’s runs, by its name, such as `sync_snowflake`.
`--limit <n>`	The most runs to list, from 1 to 1000. The default is `20`.

It also takes the global options --json, --kater-root, --scope and --help.

What each run gives

Its id, job and connection, and what started it (trigger): scheduled, manual or after. Then its status, and when it was due, queued, started and finished. A run’s status is queued, running, succeeded, failed, interrupted or cancelled.

See also