Ping Sales on any new Salesforce Sentry errors on Slack
Problem
These are corrective actions for the Duplicate Web Direct Opportunity Bug.
The issue was created on December, the 30th, however, Engineering knew about this 2 weeks earlier but failed to notice the urgency.
Proposal
- As a first step, manually ping Sales when we receive a new Salesforce error in Sentry on Slack (do we have a Slack group for this?)
- As the next iteration, we could do this automatically so SFDC errors that go to
#s_fulfillment_status
and the bot pings the Sales team automatically. - Mid-term, as we move to GCP and have Prometheus enabled, we should handle these alerts there and create a Salesforce dashboard that the teams can check and receive alerts from.
- We should think about having E2E tests that can talk to the SFDC sandbox and cover at least basic scenarios
Context:
The bug was introduced as a fix agreed with Sales for missing opportunities.
While the change was reviewed twice and tested on Staging, this was an edge case not noticed until the error appeared in production.
The team thought this could be corrected as part of the main issue and as there was only one account affected at the time dismissed it as not urgent to fix.
Edited by Teresa Tison