I'm not sure if this idea has already been added:

Sometimes (for whatever reason) the notification from the BlueCieloECM.MeridianServices.NotificationsManager fails. Causing the mail which would have been sent to be gone and the user is not notified.

In the Event Log of the server an error is logged with the reason why, however there is no way to resend this same mail. For a customer of us email notification sometimes fails because the exchange server is not responding and /or the relay server is causing is. In the event log there is an error like:

BlueCieloECM.MeridianServices.NotificationsManager: A required resource was unavailable.

However if we would send the same notification again, this would most likely succeed. What we would like to see is a retry sending a mail when it's a network related issue. So set a retry setting so the service will i.e. try 3 times before a mail is marked as error. Ofcourse a retry is not needed when i.e. the user in Meridian does not have an email.

An even better option would be to implement a queing system which handles the email notifications. So this queue can also be accessed by an admin to check for pending/failed/success messages and even resend a message from there. There already is a database which handles the subscriptions, perhaps this one can also include the email notification queue?

Kind regards.