Get training job queue context
Returns the (org, gpu_type) capacity pool the job was gated by, jobs that were holding GPU capacity in that pool when this job was submitted, and every TrainingJobStatus event in [submitted_at, released_at] for those jobs — useful for understanding why a job sat in PENDING. Caller must be an org admin and the job must belong to the caller’s org.
Authorizations
Send Authorization: Bearer <api_key>. The legacy Authorization: Api-Key <api_key> scheme is also accepted.
Path Parameters
Response
Read-only diagnostic for a training job's PENDING window.
Returns the (org, gpu_type) capacity pool the job was gated by, jobs that were holding GPU capacity in that pool when this job was submitted, and every status event in [submitted_at, released_at] for those jobs (or up to "now" if the target is still PENDING).
Hashid of the target training job
GPU type the target requested
GPUs the target requested (gpu_count * effective_node_count)
When the job row was inserted (= API POST time)
Jobs in the same (org, gpu_type) pool that were holding capacity at submitted_at
PENDING jobs in the same (org, gpu_type) pool that were ahead of the target in dequeue FIFO order at submitted_at (priority DESC then created ASC). These also block the target's release.
Every status event in [submitted_at, events_window_end] for the target job, every job in active_at_submit, and every job in pending_ahead_at_submit, oldest first.
released_at if set, else 'now' (events ongoing)
Target job's name
When the job's TRAINING_JOB_CREATED status was set, i.e. the moment it was released from PENDING. None if still PENDING.
released_at - submitted_at in seconds. None if still PENDING.
Org-level cap for (org, gpu_type). None if no cap is configured.
Team-level cap for (team, gpu_type). None if no team cap is configured.