# list_site_cron_runs

Source: https://modulify.ai/docs/api/scheduled-jobs/list-site-cron-runs

Lists recent runs of the scheduled jobs on a site, newest first, 25 to a page.

- Title: List scheduled job runs
- Scope: `config:read`
- Access: Read only
- Endpoint: `POST /v1/list_site_cron_runs`

The response carries `nextCursor`. Pass it back as `cursor` for the next page, and it is null once there is nothing more. This is the tool to reach for when you want to know why a job did not fire or what it returned.

Runs are kept for 30 days, and runs hidden with `delete_site_cron_run` or `clear_site_cron_runs` no longer appear. A [deploy hook](https://modulify.ai/docs/automations/deploy-hooks) token inside a URL comes back as `mdh_<redacted>`, because that URL can publish the site, and reading it needs `get_deploy_hook_url`. See [Scheduled jobs](https://modulify.ai/docs/automations/scheduled-jobs#read-the-run-history).

## Request

Call it with a `POST` to `https://api.modulify.ai/v1/list_site_cron_runs`, sending the inputs below as a JSON object. The token needs the `config:read` scope.

It only reads and changes nothing, so retrying it is safe.

```bash
curl -X POST https://api.modulify.ai/v1/list_site_cron_runs \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"projectId":"PROJECT_ID"}'
```

Over MCP, the same method is the [list_site_cron_runs tool](https://modulify.ai/docs/mcp/scheduled-jobs/list-site-cron-runs).

## Inputs

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `projectId` | string | Yes | The site id. |
| `cronId` | string | No | Only runs of this one job, by its id from `list_site_crons`. Leave it out for the runs of every job on the site. |
| `status` | string | No | Which runs to keep, `all`, `success`, `failure`, or `manual` for the runs someone triggered by hand rather than on the schedule. Defaults to `all`. |
| `sort` | string | No | `newest` first, the default, or `oldest` to walk the history forwards from the beginning. |
| `cursor` | string | No | The `nextCursor` from the previous page. Leave it out for the first page. |

## Response

Every call answers with the [JSON envelope](https://modulify.ai/docs/api/requests-and-responses#the-response) of `success`, `message`, `data`, `code` and `version`. `data` holds the result described above, and on a method that returns a total, `count` carries it. The [response headers](https://modulify.ai/docs/api/requests-and-responses#headers-on-every-method-call) carry the call's `X-Request-Id` and what is left of your per-minute budget in `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`. [Errors](https://modulify.ai/docs/api/errors) explains every status code a call can answer with.