---
title: "List active issues blocking campaign progress"
method: GET
path: "/issues"
tags: ["issues"]
---

# List active issues blocking campaign progress

`GET /issues`

Unified read of campaign issues — capability gaps (missing ICP/playbook), AI provider auth/billing trips, LinkedIn session expired, dispatch skip-reasons, and rate limits — all collapsed into one shape with category and severity. Pass `campaignId` to scope to a single campaign. Routine pacing (business hours, target reached, chain in progress) is intentionally NOT surfaced.

## Query parameters

- `campaignId` string
- `scope` 'active' | 'all'
- `categories` string
- `limit` integer
- `verbose` boolean

## Response `200`

Active issues for the user (and optionally a single campaign).

- object
  - `success` boolean, required
  - `issues` object[], required
    - `id` string, required
    - `campaignId` string
    - `campaignName` string
    - `source` 'skip-reason' | 'capability-gap' | 'circuit' | 'credential' | 'lifecycle', required
    - `category` 'missing-context' | 'auth' | 'billing' | 'rate-limit' | 'no-work' | 'config' | 'infra' | 'stalled', required
    - `severity` 'info' | 'warn' | 'block', required
    - `state` 'active' | 'resolved' | 'snoozed', required
    - `dedupeKey` string, required — Stable identity for cross-producer dedupe — `${category}:${campaignId|user}`, optionally suffixed with `:${reasonFamily}` for `missing-context` so distinct user actions stay separate.
    - `summary` string, required
    - `fixHint` string
    - `fixUrl` string
    - `evidence` string — Reasoner-only: human-readable evidence trail.
    - `suggestedRemediations` string[]
    - `firstSeenAt` integer, required
    - `lastSeenAt` integer, required
    - `resolvedAt` integer
    - `resolvedBy` 'manual' | 'auto' | 'sweep'
    - `raw` object
  - `total` integer, required — Total matching issues before limit
  - `hasMore` boolean, required
  - `creditsUsed` integer, required
  - `retryAfter` integer, required

## Other responses

- `400` — The server cannot or will not process the request due to something that is perceived to be a client error.
- `401` — Although HTTP specifies "unauthorized", this response means "unauthenticated". Authenticate to continue. NOTE: 401 is also returned with code "linkedin_not_connected" when the caller IS authenticated but has no connected LinkedIn account — connect LinkedIn (not re-authenticate) to continue.
- `403` — The client does not have access rights to the content.
- `404` — The server cannot find the requested resource.
- `409` — The request conflicts with the current state of the server.
- `410` — The requested content has been permanently deleted from the server.
- `422` — The request was well-formed but was unable to be followed due to semantic errors.
- `429` — Rate limit exceeded. Read error.retryAfter for the wait time in seconds.
- `500` — The server encountered a situation it does not know how to handle.
- `502` — LinkedIn returned a server error or the proxy connection failed. Retry after a few seconds.
- `503` — Proxy capacity temporarily exceeded. Retry after a few seconds.

---

[API](https://skmtc.net/berea/apis/bereach-api.md) · [All operations](https://skmtc.net/berea/apis/bereach-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/berea/bereach-api/revisions/3caf12036b26/schema)