Is there a re-drive mechanism for MongoDB triggers in Atlas? I can not find it in Atlas UI, neither can find documentation about it
My trigger function is calling a service, if the service is down at that time I can not find a way to re-drive these failed attempts later.
AWS Lambda for example, has a Dead Letter Queue so you can re-drive the failed events later if needed.
There should be some mechanism that stores failed events for a period of times and some retry logic like:
-X times every 10 minutes, if all attempts failed, send events to S3 or an SQS, and you should be able to manually retry them later or ignore them