Date |
|
Authors | |
Status | In progress |
Summary | Some CoJs signed in TIS Self-Service between the evening of 23rd July and the morning of 24th July were not correctly loaded into TIS, and hence not visible to Local Offices. |
Impact | Local Offices saw some trainees as not having signed their CoJs when they had in fact signed them. |
...
All times in BST unless indicated
: xx~15:xx00 - RabbitMQ instability begins.
: xx~15:xx00 - RabbitMQ instability ends.
: 10:30 - Missing CoJ in TIS reported.
: 16:24 - Audit of CoJ messages completed and missing CoJ resent to TIS.
Root Cause(s)
RabbitMQ became unstable due to xxxxresource limits being reached (disk-space, due to excessive messages being held and not processed).
TIS Self-Service code to submit messages to RabbitMQ did not check for successful processing.
CoJs were successfully saved within TIS Self-Service, but not received by TIS due to messaging failure.
The lack of alerting of the failures, or of the resulting data discrepancy, meant that we relied on user reports to become aware of the issue.
...