K-Rise Systems

There are plenty of times where we've questioned if an email has been sent out to the correct email address or if it was even sent out at all. I think it might be a good idea to create an audit table of emails that were sent out. The audit can store everything about the send email service that was sent so it can be resent or referenced in the future if needed. We should also include a time stamp as well as a success flag on if the email was successfully sent or not. The audit should only persist for a certain amount of time due to storage issues.

We talked about this in a call with the internal team

Ideally, if an inquiry about a specific sendemail service comes, the answer should be to look in the logs for that environment. But in talking about this, another forum post became relevant:
viewtopic.php?t=749
The log retention for certain tenants and environments is low still and needs to be reviewed so we have logs for more than a couple of hours.

See this screenshot where only 2 log files are saved: in some cases the limit is hit after only a few minutes, so here it would last less than an hour. The log retention issue/forum post will be handling that discussion

If this is for a runtime feature of recording all the emails sent across the app, this can be accomplished by inserting a record into a new app db table after each sendemail service. Then creating a webpage that shows the records from that table. For apps like EASYPay which depend on the history of emails and being able to view all on a single page, it would make sense to build this.