Our current system executes a "send web request" action from a secured, sandboxed AWS Lambda function to prevent unauthorized access to internal endpoints. However, it has been observed that the Lambda function is invoked twice when this action is executed, with the AWS client's retry logic being the apparent cause of this double invocation, rather than a manual one.

The AWS client's retry behavior suggests that there may have been a network or connection issue during the first invocation of the sandboxed Lambda. Although errors during the Lambda invocation could also trigger a retry, no errors were logged for the two requests in question.

To optimize the effectiveness of the "send web request" action and to avoid unnecessary double invocations, I propose we enhance the sandboxed Lambda function to be idempotent. This would ensure that repeated calls from the same component during the same rule execution do not have any additional effects.

Implementing idempotency would not only provide network resilience but also significantly reduce the risk of duplicate processing. It will make our system more robust, efficient, and reliable, as it ensures that regardless of how many times a request is repeated, the outcome remains the same.