-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Amazon is making is jump through more hoops in order to prevent "recursive loop" detection from affecting our Lambda functions.
To avoid potential disruption to any Lambda functions that intentionally use recursive patterns, please review the trigger configurations for the functions within your account. If any of your functions use intentionally recursive patterns, use the PutFunctionRecursionConfig API [3] to ALLOW recursive invocations on your function. If your function(s) do not use intentionally recursive patterns, no action on your part is required.
If Lambda has detected recursive loops in your account within the last three months, we have listed the affected function(s) in the 'Affected resources' tab of the AWS Health Dashboard with timestamps indicating when recursion was last detected in the format of "Function | Timestamp". If no functions are listed in the 'Affected resources' tab, we will instead list the region(s) where recursive loop detection is currently not enabled for your account.
If you do not take any action prior to November 1, 2026, we will automatically enable recursive loop detection in all regions in your account. As a result, functions that use intentional recursion may experience disruption.
If you have questions or need further assistance, please reach out to AWS Support [4].
[1] https://docs.aws.amazon.com/health/latest/ug/aws-health-planned-lifecycle-events.html
[2] https://docs.aws.amazon.com/lambda/latest/dg/invocation-recursion.html
[3] https://docs.aws.amazon.com/lambda/latest/api/API_PutFunctionRecursionConfig.html
[4] https://aws.amazon.com/support