Stop batch evaluation
Stop a running batch evaluation job. The job transitions to STOPPING and then STOPPED. Partial results from sessions that were already evaluated may be available in the response.
Stopping a batch evaluation is useful when you realize the job was started with incorrect parameters, or when you no longer need the results.
Code samples
Example
Request parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
|
|
String |
Yes |
The batch evaluation ID to stop. Passed as a path parameter. |
Response
| Field | Type | Description |
|---|---|---|
|
|
String |
The batch evaluation ID. |
|
|
String |
ARN of the batch evaluation. |
|
|
String |
Updated status: |
Errors
| Error | HTTP status | Description |
|---|---|---|
|
|
404 |
No batch evaluation found with the specified ID. |
|
|
409 |
The batch evaluation is not in a state that can be stopped (for example, already completed or stopped). |
|
|
400 |
Invalid batch evaluation ID format. |
|
|
403 |
Insufficient permissions. |
|
|
429 |
Request rate exceeded. |
|
|
500 |
Service-side error. |