Skip to main content
After creating evaluations (via create() or run()), they start in PENDING status while the evaluation engine processes them. Use wait_for() to block until all evaluations have completed. An evaluation is considered complete when its status is anything other than PENDING: SUCCESS, FAILED, SKIPPED, PENDING_HUMAN, or CANCELLED.

Usage

Wait for specific evaluations you already have IDs for — typically from create() or from a run() with an agent.Returns evaluations in the same order as the input evaluation_ids.Create and wait:
Custom timeout and poll interval:
Full lifecycle — run() with agent, then wait_for():

Returns

A list of Evaluation objects once all have left PENDING status. When using evaluation_ids, results are in the same order as the input. When using job_id, no specific result ordering is guaranteed.

Parameters

list[str]
A list of evaluation IDs to wait for. Mutually exclusive with job_id.
str
The job ID returned by run() in endpoint-connection mode. Mutually exclusive with evaluation_ids.
int
default:"300"
Maximum seconds to wait before raising TimeoutError. When using job_id, this covers both the job polling and evaluation polling phases.
int
default:"5"
Seconds to sleep between polling cycles.

Errors