# Monitor A Job (/docs/monitor)



# Monitor A Job [#monitor-a-job]

Use `mn job monitor` when you already have a job id and want to stream its events.

## Start Monitoring [#start-monitoring]

```bash
mn job monitor <job_id>
```

Expected output includes job events as they arrive.

If you do not know the job id:

```bash
mn job list
```

Expected output includes:

```text
Job ID
```

## Fetch Results [#fetch-results]

```bash
mn job result <job_id>
```

This fetches final and progressive results for a job when the bundle emits them.

## Inspect Status [#inspect-status]

```bash
mn job status <job_id>
```

Expected output includes:

```json
{
  "status": "running"
}
```

Terminal statuses are:

* `completed`
* `failed`
* `cancelled`

## Cancel A Job [#cancel-a-job]

```bash
mn job cancel <job_id>
```

Expected output:

```text
Job cancelled. Status: cancelled
```

## System Overview [#system-overview]

For a broader view of nodes and jobs:

```bash
mn node list
mn runtime metrics
```

Expected `mn node list` output includes:

```json
{
  "nodes": [],
  "jobs": []
}
```

In a cluster, `nodes` contains connected runtime nodes and executor pool stats.

## Operational Notes [#operational-notes]

* Closing your terminal does not necessarily cancel a submitted job.
* Use `mn job cancel <job_id>` to stop service workflows.
* Use `mn job dead-letters <job_id>` when messages fail to route or process.
* Run `mn job clear` only when you are ready to remove terminal job records.

## Related Pages [#related-pages]

* [CLI Reference](cli.md)
* [API Reference](api.md)
* [Troubleshooting](troubleshooting.md)