Catch expected Auth0 errors instead of causing alerts
@DSASanFrancisco/portal-members
Summary
- Instead of letting user already exists (status code 409) from Auth0 propagate all the way back to Flask to be reported as an unexpected error on Sentry (and thus trigger alerts), we catch and log the error where appropriate.
I have:
-
Included a summary of the changes -
Linked to this merge request from AirTable -
Add all dependent merge requests
Edited by Jeff May