Predict.aiDocs
Pipelines

Train now

Trigger a training run on demand — and every reason the platform might say no.

Don't want to wait for the schedule? Queue a run immediately:

curl -X POST "$API_BASE/v1/pipelines/$PIPELINE_ID/train" \
  -H "Authorization: Bearer $TOKEN" \
  -H "X-Workspace-Id: $WORKSPACE_ID"
{
  "data": {
    "uid": "9f2c41d8-…",
    "manual_train_requested": true,
    "message": "Training queued."
  }
}

There is no request body — the pipeline ID in the path is all it needs. The 202 means the run is queued, not started — the training dispatcher picks it up within seconds. Follow progress in Trainings, or subscribe to the workspace's realtime channel for training.job.* events.

If the pipeline lists several models in its model pool, the queued cycle trains all of them.

Pre-flight checks

The train call validates everything before queueing, so failures are immediate and actionable rather than silent:

StatusWhyWhat to do
404Pipeline not found, or not yoursCheck the ID and workspace.
409Pipeline is pausedSet active: true first.
409A run is already in flightWait for it to complete.
429Training concurrency or daily quota reachedWait, or spread runs out.
403Fine-tuning isn't in your plan (foundation pipelines)Upgrade, or use zero-shot deployment instead.
402Insufficient credits for an upfront-charged runTop up, or lower training_intensity.
{
  "status": "Insufficient credits to start training (need 40, have 12). Top up your balance or pick a lower training intensity, then try again."
}

What a run costs

Foundation trainings charge upfront based on training_intensity. Custom-code trainings bill by elapsed compute after the run. Estimate either kind before you spend with POST /v1/billing/estimate.

On this page