---
title: "List follow-up loops"
method: GET
path: "/v1/cron-jobs/loops"
tags: ["cron-jobs"]
---

# List follow-up loops

`GET /v1/cron-jobs/loops`

## Request

- Base URL: `https://api.patricia.app` (the document declares no server; this is the origin it was published from)
- URL: `https://api.patricia.app/v1/cron-jobs/loops`
- Auth: HTTP bearer

The follow-ups Patricia is running behind the scheduled tasks you can see: the reason, the checks used, and when each one ends. Creator scoping matches the list route: your own by default, the team view (`mine=false`) for admins. Not paginated.

## Query parameters

- `mine` boolean: When true (default) list only the caller's OWN scheduled jobs. Set false for the team/all view (admins/owners only). That view also includes jobs with no resolved creator.
- `created_by` string, uuid, nullable: Filter to one creator actor id (admins/owners only; others are always scoped to self).

## Headers

- `X-Tenant-Id` string, nullable

## Response `200`

One row per live or waiting follow-up loop whose task is visible.

- CronJobLoopsResponse: The live follow-up loops behind the scheduled tasks the caller can see.
  - `items` CronJobLoop[], required
    - `cron_job_id` string, uuid, required
    - `loop_id` string, uuid, required
    - `kind` string, required
    - `status` string, required
    - `subject` string, required
    - `reason` string, required
    - `checks_used` integer, required
    - `max_checks` integer, required
    - `ends_at` string, date-time, required

## Other responses

- `400`: Bad request
- `401`: Unauthorized
- `403`: Forbidden. Inspect response body `code` for the specific reason (for example: PERMISSION_DENIED, EMAIL_NOT_VERIFIED, TENANT_ACCESS_REQUIRED, ROLE_UNRESOLVED)
- `422`: Validation error

---

[API](https://skmtc.dev/patricia/apis/patricia-api.md) · [All operations](https://skmtc.dev/patricia/apis/patricia-api/llms.txt) · [OpenAPI document](https://skmtc.dev/patricia/apis/patricia-api/revisions/0dfb44495ea1?raw)