AWS Lambda Destinations Not Triggering for scenarios Invocations in Python 3.8 Runtime
I'm stuck on something that should probably be simple... I need some guidance on I'm working through a tutorial and I keep running into Hey everyone, I'm running into an issue that's driving me crazy..... Hey everyone, I'm running into an issue that's driving me crazy. I’ve set up an AWS Lambda function using the Python 3.8 runtime, and I configured a destination for asynchronous invocations to handle failed executions. However, I'm not seeing the configured destination being triggered when the function fails. Here’s the relevant configuration I have: ```python import json def lambda_handler(event, context): try: # Simulate a failure result = 1 / 0 # This will raise a ZeroDivisionError return { 'statusCode': 200, 'body': json.dumps(result) } except Exception as e: print(f'behavior occurred: {e}') raise e # Rethrow to trigger the failure destination ``` I set the destination for failed executions in the console as follows: - **Destination Type**: Lambda Function - **Function ARN**: arn:aws:lambda:us-east-1:123456789012:function:FailureHandler I also ensured that the FailureHandler function has the appropriate IAM permissions to be invoked by the initial Lambda function. Despite this setup, I see no logs or invocations in the FailureHandler function when the ZeroDivisionError occurs. I've checked CloudWatch logs for both the original and the destination function, but I can’t find any indication that the failure destination is even being reached. I've tested the setup by manually invoking the function through the AWS console, and while the original function logs the behavior correctly, the destination never gets called. Any ideas why the destination is not being triggered? Are there specific configurations I might be missing regarding Lambda's asynchronous invocation behavior? I'm working on a CLI tool that needs to handle this. Any ideas what could be causing this? I'd really appreciate any guidance on this. I'm working in a CentOS environment. Could this be a known issue? This is happening in both development and production on Ubuntu 22.04. I recently upgraded to Python 3.9. Thanks for taking the time to read this! My development environment is Windows 11. Is this even possible?