200
The pipeline has finished processing inputs associated with the provided completion token. Schema — OPTIONAL |
---|
status stringPossible values: [complete , inprogress ] Completion token status returned by the /completion_status endpoint. |
|
202
The pipeline is still processing inputs associated with the provided completion token. Schema — OPTIONAL |
---|
status stringPossible values: [complete , inprogress ] Completion token status returned by the /completion_status endpoint. |
|
404
Pipeline with that name does not exist Schema — OPTIONAL |
---|
details objectDetailed error metadata.
The contents of this field is determined by error_code . | error_code stringError code is a string that specifies this error type. | message stringHuman-readable error message. |
|
410
Completion token was created by a previous incarnation of the pipeline and is not valid for the current incarnation. This indicates that the pipeline was suspended and resumed from a checkpoint or restarted after a failure. Schema — OPTIONAL |
---|
details objectDetailed error metadata.
The contents of this field is determined by error_code . | error_code stringError code is a string that specifies this error type. | message stringHuman-readable error message. |
|
Schema — OPTIONAL |
---|
details objectDetailed error metadata.
The contents of this field is determined by error_code . | error_code stringError code is a string that specifies this error type. | message stringHuman-readable error message. |
|
Schema — OPTIONAL |
---|
details objectDetailed error metadata.
The contents of this field is determined by error_code . | error_code stringError code is a string that specifies this error type. | message stringHuman-readable error message. |
|