List future scheduled jobs
GET /admin/jobs/scheduled
Returns pending jobs scheduled for a future time.
You need to be signed in with system.jobs.read or system.admin for the whole install; a permission held only for a team doesn’t count.
Only rows with status pending and a non-null scheduled_for strictly later than the database query time are included. Results are sorted by scheduled_for, soonest first, and equal times have no further order. Due, unscheduled and non-pending jobs are left out. A listed row can still be unclaimable because it has reached its attempt limit.
Page with limit and offset; the default is 50 and the maximum is 200. The page and total are separate reads, and time passing, claims and concurrent writes can make them disagree or move rows between pages. With no matches, items is empty and total is zero; an offset past the end can return an empty page with a positive total.
The database calculates due_in_seconds and rounds it to an integer, so a future job can show zero just before it’s due. A schedule sets the earliest time a worker may claim the job, not a promised start time. This endpoint lists queued rows; it doesn’t define recurring schedules or offer a scheduling editor.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”Maximum number of items to return, from 1 to 200; defaults to 50. After conversion to a 32-bit integer, values of 0 or less use 50 and values above 200 use 200.
Number of matching rows to skip. Use a non-negative integer; the default is zero.
Responses
Section titled “ Responses ”A page of future pending jobs and a separately read total.
A page of pending jobs whose schedule is still in the future.
object
Future pending jobs on this page, ordered by scheduled time. Empty when no rows match the page.
A pending job with a scheduled time later than the database query time.
object
UUID of the job row.
Stored job type.
Stored status; this endpoint selects pending rows only.
Stored queue priority. Once the schedule is due, lower values are considered first among eligible, unlocked jobs.
Claims recorded since creation or administrative requeue. A future schedule doesn’t mean another attempt remains.
Maximum claim count used by workers.
Earliest time the job may be claimed, not a guaranteed start time. Always present on rows this endpoint returns.
Original enqueue time, preserved across retries.
Seconds until scheduled_for, calculated by the database and rounded to an integer. It can be zero for a job due in under half a second.
Future pending rows across all pages, counted in a separate query. Time passing or concurrent changes can make it disagree with items.
Authentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}Authenticated but missing required capabilities
object
Human-readable error summary
Example
the request could not be completed