SOP 3rd Party Integration Error Handling

Sighten's app integrates with a multitude of 3rd party organizations. We rely on these organizations to store and transmit our data (i.e. contracts (Docusign), Address Validation (Google Maps), Sendgrid (Email Delivery).

Occasionally we will experience a connection timeout for one of these orgs and this shows up as an error in Sentry. When this happens, we should be assessing the severity of the issue (How frequently is this occurring? How many unique users is this timeout affecting?). Most times the timeout is just a singular blip with negligible impact to our customers, but we still want to check if the 3rd party org is experiencing a major outage.

This process of checking is unique to the org and would involve us a look at an org's dashboard (there may be a LastPass login to check a dashboard for the org) or contacting a representative from the org (see this link for 3rd party org contact list).

Follow this link for contacts

• Docusign

• Plot.ly

  • https://sighten.atlassian.net/browse/SEN-11

• Google Maps

• Docraptor

  • https://sighten.atlassian.net/browse/SEN-8

  • SEN-404 - Getting issue details... STATUS

  • SEN-157 - Getting issue details... STATUS

• Box
  • SEN-262 - Getting issue details... STATUS

• CloudConvert

• CloudHub

  • SEN-422 - Getting issue details... STATUS

• AWS

• FullStory

• Loggly

• Sendgrid

  • SEN-252 - Getting issue details... STATUS

  • 

  • Sign into SendGrid and check primary dashboard for the following: 

    • Bounce Rate (shouldn't exceed 0.5%)

    • Emails Delivered Rate (shouldn't dip below 95%)

• Salesforce

  • https://sighten.atlassian.net/browse/SEN-13