Ravindra BagaleCourses & study guides मराठी Track your progress

Ravi Sir's Cards › AWS

Retry and Catch

This revision card explains Retry and Catch. A flaky payment API should not fail the whole order on the first timeout. It describes retry repeats a Task on named errors with backoff. Catch routes failure to a cleanup or alert state. The how-to section covers how to add Retry for States.TaskFailed and Lambda.ServiceException; Catch unknown errors to a notify Fail state. An example on the card is execution history shows three retries then Catch path when the API stayed down.

Retry and Catch A flaky payment API should not fail the whole order on the first timeout. Retry repeats a Task on named errors with backoff. Catch routes failure to a cleanup or alert state. Add Retry for States.TaskFailed and Lambda.ServiceException; Catch unknown errors to a notify Fail state. Execution history shows three retries then Catch path when the API stayed down.
Retry and Catch · Download PNG
Read card text

What this card says

Why do we need it?

A flaky payment API should not fail the whole order on the first timeout.

What is it?

Retry repeats a Task on named errors with backoff. Catch routes failure to a cleanup or alert state.

Retry / Catch

How to do it

Add Retry for States.TaskFailed and Lambda.ServiceException; Catch unknown errors to a notify Fail state.

Example

Execution history shows three retries then Catch path when the API stayed down.

See all AWS revision cards