Date |
| ||||||||
Authors | |||||||||
Status | Documenting
| ||||||||
Summary | |||||||||
Impact | Staff would have had to resubmit recommendations after the fix was introduced. |
| Table of Contents |
|---|
Non-technical Description
...
5 Whys (or other analysis of Root Cause)
Why was the user seeing both a success and fail message on submission of recommendation?
The error handling on the client for submission to GMC method is not set up correctly and will always show both messages whenever there is an errorWhy was the user seeing the error message in the browser?
An error was thrown in the client application on calling the submit to GMC endpoint but no details of the error were captured by the FE
Recommendation service contained no logs for submitting recommendations to GMCWhy were no logs showing in recommendation servicefor submissions in recommendation, profile or integration services?
Requests were failing at the API Gateway and not reaching the other services - hence nothing to log.Why were request for submission failing at API Gateway?
Requests toprod-revalidation-api-gateway-authoriserLambda were reaching the 3 second timeout limit. However, all other requests to this function were not failing, just submissions.Why were just submissions crashing in the Lambda and not saving, for example?
????
...
Action Items
Action Items | Owner | Comments |
|---|---|---|
Fix error handling in UI for submissions to GMC | ||
Extend logging in Lambda authoriser | ||
Set an alarm when authoriser is approaching/hitting the timeout maximum | ||
...