A Database Trigger has been Suspended
A database trigger RealmABC has failed in your application AWSEventBridge and has been suspended. This trigger will not run until it can be successfully resumed. Please use the following link to view the trigger’s configuration and address the problem.
Resumed trigger multiple times but not worked
maximum attempts (10) reached processing event for trigger id=we232391a9a719732e21a3c5e: ValidationException: Total size of the entries in the request is over the limit. status code: 400, request id: 232233-9273-4587-962b-c4b41ddcf3e3
Hi @Balraj_Yadav,
Welcome to MongoDB Community.
It looks like the database trigger is failed to tail the operations and needs to be manually resumed.
There is a high chance that you have too small oplog for your workload and triggers fall off it. If this is the case you will have to resume without the resume token checkbox as there is no way to resume it otherwise…
In any case I suggest to contact MongoDB support for further analysis.
Best regards,
Pavel
After facing the same issue I have discovered that a trigger will get suspended if the function he is trying to run encountered an error and fails. You may try to see if the function runs correctly from the Atlas App Services console. If it fails - try to fix the function’s bug and resume the trigger afterwards.
Best regards,
Omri