Loops

Resolve capacity and quota errors and stop a run after an interruption.

Resolve capacity and quota errors

Use the error message and HTTP status code to choose the next step:

Status	Error message	What to do
`429`	`Could not schedule trainer. Please try again later.`	Retry later. If the error persists, contact support with your model, sequence length, and full error message.
`403`	`Your organization has reached its Loops trainer capacity. Stop an existing trainer deployment or contact your Baseten representative to raise the limit.`	Deactivate a run to free trainer GPUs, or request a higher limit for the concurrency you need.

This 429 means no eligible GPU capacity is available. Loops rejects the request before creating a trainer or run instead of queuing it.

Resolve accelerator errors

If provisioning fails with either of these messages, contact your organization admin or Baseten support:

accelerator priority ... has no overlap with your organization's allowlist: The requested GPU type isn’t permitted by your organization’s configuration.
has no candidate on those accelerators: The permitted GPUs don’t support the requested model and sequence length.

Include the model ID, maximum sequence length, and full error message.

Stop a run after an interruption

An SDK timeout stops the client from waiting; it doesn’t stop the work on Baseten. If your script or machine stops before cleanup, deactivate the run before retrying. Use the run_id saved by your script. If you only have a session_id, find the run first. Set your API key and run ID:

export BASETEN_API_KEY="YOUR_API_KEY"
export RUN_ID="YOUR_RUN_ID"

Baseten CLI
REST API

Use the Baseten CLI to deactivate the run. --yes skips the confirmation prompt:

baseten loops run deactivate --run-id "$RUN_ID" --yes

Then check the run’s status:

baseten loops run describe --run-id "$RUN_ID" \
  --jq '{run: .status.name, sampler: .sampler.status.name}'

Call Deactivate a run:

curl --fail-with-body --request POST \
  "https://api.baseten.co/v1/loops/runs/$RUN_ID/deactivate" \
  --header "Authorization: Bearer $BASETEN_API_KEY"

Then call Get a run and check run.status.name and run.sampler.status.name in the response:

curl --fail-with-body \
  "https://api.baseten.co/v1/loops/runs/$RUN_ID" \
  --header "Authorization: Bearer $BASETEN_API_KEY"

Confirm that the run and sampler report INACTIVE. If the run never created a sampler, sampler is null.

Find a run from its session ID

The training client can time out before returning a run ID. If your script saved a session_id, list your runs and find the matching session.

Baseten CLI
REST API

List your runs and filter by the saved session ID. Replace YOUR_SESSION_ID with that value. --all includes inactive runs:

baseten loops run list --all \
  --jq '.runs[] | select(.session_id == "YOUR_SESSION_ID") | {id, status}'

Call List runs:

curl --fail-with-body \
  "https://api.baseten.co/v1/loops/runs" \
  --header "Authorization: Bearer $BASETEN_API_KEY"

In the response’s runs array, find the entry whose session_id matches your saved value.

Use the matching run’s id as RUN_ID in the deactivation command. If its status is already INACTIVE, it doesn’t need deactivation.

Get started

Model APIs

Inference

Training

Sandboxes

Development

Deployment

Engines

Model Labs

Organization

Hosting options

Observability

Troubleshooting

Resolve capacity and quota errors

Resolve accelerator errors

Stop a run after an interruption

Find a run from its session ID

​Resolve capacity and quota errors

​Resolve accelerator errors

​Stop a run after an interruption

​Find a run from its session ID

Resolve capacity and quota errors

Resolve accelerator errors

Stop a run after an interruption

Find a run from its session ID