Lambda Retry Behavior
Retry semantics follow the invocation path: synchronous errors are the caller's problem; asynchronous invokes are retried twice with backoff, then routed to an on-failure destination or dead-letter queue; event source mappings retry a failing batch until success or expiry unless you configure max attempts, bisection, or partial-batch responses to isolate the poison record. Timeouts and throttles count as failures.
This Concept is waiting for its first lesson!
Retry semantics follow the invocation path: synchronous errors are the caller's problem; asynchronous invokes are retried twice with backoff, then routed to an on-failure destination or dead-letter queue; event source mappings retry a failing batch until success or expiry unless you configure max attempts, bisection, or partial-batch responses to isolate the poison record. Timeouts and throttles count as failures.
Are you a teacher? Sign in to start contributing.
Sign In