I find these scattered across all cloud systems when I am just looking at suspended tasks and only if I happen to be looking at the right process since there is no global report of suspended tasks available.

They sit in suspension because the rules server was offline at the time it was called for and these wait for someone like me to come in and click retry but then the information does not get to the departments until months or even a year later which impacts the submitter making them not trust the form is processing their requests in a timely manner.

If the rule system is offline, it should re-trigger all suspended events when it comes back online. It should be part of the boot up process.