1 Answer
- Newest
- Most votes
- Most comments
2
Hi, I don't have access to your account and can neither see your resources nor the event records.
How are you triggering the "recurring Lambda scheduler". Is this via Amplify or EventBridge (CloudWatch Events) or something else?
I would check the following:
- Any other possible triggers of the lambda itself.
- Are there any errors on the lambda running? If so, it's possible that the retry functionality could have kicked off another run of the lambda.
- What does the timeout look for your lambda function?
- Lastly, I would check the idempotency of the function. This guide may be helpful: https://aws.amazon.com/premiumsupport/knowledge-center/lambda-function-idempotent/
answered 3 years ago
Relevant content
- asked 2 years ago
- asked 10 months ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 12 days ago
- AWS OFFICIALUpdated 2 years ago
The Lambda is triggered via Amplify. No triggers are present for lambda except the Recurring Scheduler The timeout of lambda function is 15 minutes. There are no errors ,while trigger-1 was runnings till ,then another trigger was triggered