Skip to content
Artist Alley

List scheduled actions

GET
/admin/scheduled-actions

The “Scheduled actions” admin surface (ADR 0020). Lists every scheduled action — pending, done, cancelled and failed — newest first, so an operator can see what is queued to fire, cancel it before it does, and review what already ran. Filter by state to narrow to a single lifecycle bucket.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Query Parameters

Section titled “Query Parameters ”
state
string
Allowed values: pending done cancelled failed

Narrow to one lifecycle state.

limit
integer
default: 50 >= 1 <= 200
cursor
string

Opaque next-page token from a prior response.

Responses

Section titled “ Responses ”

200

Section titled “200 ”

A page of scheduled actions, newest first.

object
items
required
Array<object>

One row of the scheduled_actions table (ADR 0020) — a declarative future action executed by the reaper through the jobs queue.

object
id
required
string format: uuid
action
required
string
Allowed values: restrict delete change_state change_sensitivity notify
target_kind
required
string
Allowed values: asset post collection user
target_id
required

The target’s id as text. A UUID for asset/post/collection, a user ref for user — the column is polymorphic across both.

string
params

Per-action parameters. For change_sensitivity, a to field naming the target tier; for change_state, a to_state code; for delete, an optional reason.

object
key
additional properties
any
scheduled_for
required
string format: date-time
state
required
string
Allowed values: pending done cancelled failed
error

Failure message when state is failed; null otherwise.

string
nullable
created_by

User who scheduled it; null for system-scheduled actions.

integer format: int64
nullable
created_at
required
string format: date-time
executed_at

When the reaper ran it; null while pending or cancelled.

string format: date-time
nullable
next_cursor
string
nullable

401

Section titled “401 ”

Authentication required, missing, or invalid

object
error
required

Human-readable error summary

string
Example
the request could not be completed
Example
{
  "error": "authentication required: sign in and retry with a valid session or API token"
}

403

Section titled “403 ”

Authenticated but missing required capabilities

object
error
required

Human-readable error summary

string
Example
the request could not be completed