Date |
| ||||||||
Authors | |||||||||
Status | Documenting
| ||||||||
Summary | Display error message on Reval ‘under notice’ ( | ||||||||
Impact | For approximately 90 minutes, some requests to do anything with recommendations (including doctor’s details) didn’t work |
| Table of Contents |
|---|
Non-technical Description
Users on Revalidation were experiencing/receiving error messages, e.g. when searching for ‘Under Notice’ doctors. No records were showing. This is because a request to replace the tasks for the recommendation feature, called a “deployment”, was mistakenly bringing in tasks that were being identified as healthy before they were ready to take user’s requests.
A little over an hour after the deployment began, the service did eventually reach a point were the tasks that were taking requests did fully start up before receiving requests. The TIS team have been giving their focus to improvements in the application defined as higher priority so are yet to address the way that tasks are identified as healthy or unhealthy. As part of another incident, more resource was made available to the tasks and that meant that they are ready to take requests much quicker.
Trigger
Re-deployment
Detection
...
Action Items | Owner | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Increased service resources (CPU): Tasks now start more quickly | DONE | |||||||||||||||||||||||||
| Won’t do. | |||||||||||||||||||||||||
Cards are still outstanding for improving the observability of the services |
|
...