Investigate & provide mechanism to avoid errors that should not be tracked

Problem

We have been spending a lot of time each week trying to look into revenue impact and Salesforce errors which probably did not cause any errors to the execution of the codebase and are there just to be logged as errors.

Ex -

• "Operation failed due to a lock competition, please retry later." (link)
• "Update SaaS User Count error" (link
• "Reconciliation could not be updated" (link)

Proposal

We need to have a mechanism in place which could help avoid these errors being stored within the database and should only be logged.

Next steps (if any)

Create another issue to look at the end of each month to see if any of the errors occuring during the course of the whole are not needed anymore.