---
title: "List a comment automation's runs"
method: GET
path: "/comment-automations/{id}/runs"
tags: ["Comment automations"]
---

# List a comment automation's runs

`GET /comment-automations/{id}/runs`

## Request

- Base URL: `https://api.rizamo.com/v1`
- URL: `https://api.rizamo.com/v1/comment-automations/{id}/runs`
- Auth: HTTP bearer

One run per matched comment, newest first, a page at a time: pass `nextCursor` as `cursor` for the next one. A run stays when its comment is deleted, but its `threadId` may then be gone from the inbox, and a private reply not sent yet is skipped (`refused`).

## Path parameters

- `id` string, required: The comment automation's id (`cauto_`).

## Query parameters

- `status` 'pending' | 'waiting' | 'sent' | 'skipped' | 'failed' | 'expired': pending: going out within minutes. waiting: the follow gate asked and waits for their reply. sent: the message with the link went out. skipped, failed, expired: `reason` says why.
- `cursor` string: `nextCursor` from the page before.
- `limit` integer: How many to return, up to 100: 50 when left out.

## Response `200`

OK

- object
  - `items` CommentAutomationRun[], required
    - `id` string, required
    - `automationId` string, required
    - `threadId` string, required: The comment's thread in the inbox. It may be gone: deleting a thread's first comment deletes the thread (`Delete a comment`), and `Get a thread` then answers not found.
    - `conversationId` string, nullable, required: The inbox thread of the private conversation, once the private reply went out.
    - `commentId` string, required: The comment on the network.
    - `comment` string, required: The comment's text.
    - `commenter` object, required
      - `name` string, required
      - `handle` string, required
    - `commentedAt` string, date-time, required
    - `status` 'pending' | 'waiting' | 'sent' | 'skipped' | 'failed' | 'expired', required: pending: going out within minutes. waiting: the follow gate asked and waits for their reply. sent: the message with the link went out. skipped, failed, expired: `reason` says why.
    - `reason` 'already_sent' | 'too_old' | 'refused' | 'unclear' | 'expired', nullable, required: already_sent: this person already got this automation's message, or may have (an unclear one). too_old: the comment was more than 7 days old when Rizamo got to it, past Meta's window. refused: Meta refused this message, such as a person who does not take messages, or a comment that already got its one private reply (another app or team with the account sent first), or would have: the comment was deleted before the message went out (skipped); the run's `error` says which. unclear: Rizamo could not tell whether it went out, so it never sends it again. expired: the follow gate got no reply within 7 days of its last message. A refused login or permission is no reason here: the automation is paused with it, and its runs wait as they were, to go out once it is resumed within the 7 days.
    - `error` string, nullable, required: What Meta answered, when it refused.
    - `followGate` 'asked' | 'reminded' | 'followed' | 'expired', nullable, required: Where the person is in the follow gate. Null without one.
    - `publicReply` string, nullable, required: The public reply posted under the comment.
    - `sentAt` string, date-time, nullable, required: When the message with the link went out.
    - `updatedAt` string, date-time, required
  - `nextCursor` string, nullable, required: Null on the last page.

## Other responses

- `400`: `invalid_request`: A field is missing or wrong, or the request cannot be done as asked: the message names the field or says what to change.
- `401`: `unauthorized`: No API key or sign-in, or the key does not work: it was deleted, or it expired.
- `403`: `forbidden`: The caller may not do this: the key or agent lacks the scope (the message names it), or the action needs another role or a fresh sign-in.
- `404`: `not_found`: No such object, or it is outside your team or the profiles your key reaches.
- `429`: `rate_limited`: Over one of Rizamo's limits, or a network asked Rizamo to slow down: wait for `Retry-After` seconds, or as long as the message says.
- `500`: `internal`: Our side failed: retry, and send the `requestId` if it keeps failing.
- `503`: `timeout`: The request took too long to work out, most often a report: try again in a moment, or ask a report for a shorter period or one profile.

---

[API](https://skmtc.dev/rizamo/apis/rizamo-api.md) - [All operations](https://skmtc.dev/rizamo/apis/rizamo-api/llms.txt) - [OpenAPI document](https://skmtc.dev/rizamo/apis/rizamo-api/revisions/31b0c1b1ffb5?raw)
