> ## Documentation Index
> Fetch the complete documentation index at: https://headgate.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Job detail — attempts timeline, errors, and per-attempt logs.

> River's detail view shows a timeline plus a per-attempt section with timing, the
error, and execution logs (its `riverlog` middleware persists them to the job).
Per-attempt logs are the difference between "it failed again" and knowing why, so
the envelope carries them rather than sending the operator to a log aggregator
with a job id and hope. `include_payload` applies here too.




## OpenAPI

````yaml /api/headgate.openapi.yaml get /jobs/{id}
openapi: 3.1.0
info:
  title: headgate control API
  version: 0.1.0
  description: >
    The web UI is one client of this control API and gets no

    privileged access — asynqmon reads Redis directly, which is why its
    compatibility

    note is three minor versions stale.


    Both the Go and Rust implementations serve this spec, and the conformance
    suite

    asserts identical responses. Every list endpoint is bounded to prevent
    inspection

    from becoming an unbounded store operation: asynq's

    GetQueueInfo is O(number of groups) and has pinned Redis CPU for seconds in

    production. Monitoring caused the outage.


    DERIVED FROM THE ARCHITECTURE, NOT FROM A PREDECESSOR'S UI. The first draft
    of this

    spec was the asynq Inspector surface -- list by state, act on one job, pause
    a queue

    -- with new nouns bolted on. That inherited three problems: it omitted bulk

    operations, history, and enqueue (which asynq and apalis-board respectively
    DO have),

    and more importantly it had no endpoint for the question this system's own
    design

    creates. When dequeue is an admission decision, the operator's first
    question is not

    "what is in the queue" but "why is THIS job not running" -- see
    /jobs/{id}/admission.

    No predecessor needs that endpoint because no predecessor has a gate.
servers:
  - url: /api/v1
security: []
paths:
  /jobs/{id}:
    get:
      summary: Job detail — attempts timeline, errors, and per-attempt logs.
      description: >
        River's detail view shows a timeline plus a per-attempt section with
        timing, the

        error, and execution logs (its `riverlog` middleware persists them to
        the job).

        Per-attempt logs are the difference between "it failed again" and
        knowing why, so

        the envelope carries them rather than sending the operator to a log
        aggregator

        with a job id and hope. `include_payload` applies here too.
      parameters:
        - $ref: '#/components/parameters/Id'
        - name: include_payload
          in: query
          schema:
            type: boolean
            default: false
      responses:
        '200':
          description: OK
components:
  parameters:
    Id:
      name: id
      in: path
      required: true
      schema:
        type: string

````