#[non_exhaustive]
pub enum StopPipelineExecutionErrorKind {
ConflictException(ConflictException),
DuplicatedStopRequestException(DuplicatedStopRequestException),
PipelineExecutionNotStoppableException(PipelineExecutionNotStoppableException),
PipelineNotFoundException(PipelineNotFoundException),
ValidationException(ValidationException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the StopPipelineExecution
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
ConflictException(ConflictException)
Your request cannot be handled because the pipeline is busy handling ongoing activities. Try again later.
DuplicatedStopRequestException(DuplicatedStopRequestException)
The pipeline execution is already in a Stopping
state. If you already chose to stop and wait, you cannot make that request again. You can choose to stop and abandon now, but be aware that this option can lead to failed tasks or out of sequence tasks. If you already chose to stop and abandon, you cannot make that request again.
PipelineExecutionNotStoppableException(PipelineExecutionNotStoppableException)
Unable to stop the pipeline execution. The execution might already be in a Stopped
state, or it might no longer be in progress.
PipelineNotFoundException(PipelineNotFoundException)
The pipeline was specified in an invalid format or cannot be found.
ValidationException(ValidationException)
The validation was specified in an invalid format.
Unhandled(Unhandled)
An unexpected error occurred (e.g., invalid JSON returned by the service or an unknown error code).
When logging an error from the SDK, it is recommended that you either wrap the error in
DisplayErrorContext
, use another
error reporter library that visits the error’s cause/source chain, or call
Error::source
for more details about the underlying cause.