View a markdown version of this page

ðŸ”Ĩ āļ‚āđˆāļēāļ§āļ”āđˆāļ§āļ™: transfer/latest/userguide/API ExecutionError.html - āļ›āļĢāļ°āđ€āļ”āđ‡āļ™āļĢāđ‰āļ­āļ™

ExecutionError

Specifies the error message and type, for an error that occurs during the execution of the workflow.

Contents

Message

Specifies the descriptive message that corresponds to the ErrorType.

Type: String

Required: Yes

Type

Specifies the error type.

  • ALREADY_EXISTS: occurs for a copy step, if the overwrite option is not selected and a file with the same name already exists in the target location.

  • BAD_REQUEST: a general bad request: for example, a step that attempts to tag an EFS file returns BAD_REQUEST, as only S3 files can be tagged.

  • CUSTOM_STEP_FAILED: occurs when the custom step provided a callback that indicates failure.

  • INTERNAL_SERVER_ERROR: a catch-all error that can occur for a variety of reasons.

  • NOT_FOUND: occurs when a requested entity, for example a source file for a copy step, does not exist.

  • PERMISSION_DENIED: occurs if your policy does not contain the correct permissions to complete one or more of the steps in the workflow.

  • TIMEOUT: occurs when the execution times out.

    Note

    You can set the TimeoutSeconds for a custom step, anywhere from 1 second to 1800 seconds (30 minutes).

  • THROTTLED: occurs if you exceed the new execution refill rate of one workflow per second.

Type: String

Valid Values: PERMISSION_DENIED | CUSTOM_STEP_FAILED | THROTTLED | ALREADY_EXISTS | NOT_FOUND | BAD_REQUEST | TIMEOUT | INTERNAL_SERVER_ERROR

Required: Yes

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following: