...
GMC have not elaborated on the cause or resolution
GMC got back to HEE on 19 January 22 by an email. They applied a security patch in their BE environment. The webserver serving the API was’t included in the first patch, so it was not tested.
They have now included it in the testing plan to ensure that this is not repeated again.
...
Timeline
- 00:05 alert send by nightly job to Slack
- 09: 50 reran job to see if it was a temporary network error. Adewale Adekoya sent an email to GMC asking if the problem could be looked into
- Began investigating with GMC.
- 00:05 GMC-Sync succeeded
- 09:20 Re-attempted changing connetions but this failed
- Issue narrowed down to an IP address but this hasn’t resolved the issue
- Further debugging info has been exchanged
- A further fix did not resolve the issue, and
- Sync job ran successfully however no updates from GMC on any changes made on their side
- Adewale Adekoya further enquires for any updates from the GMC but no response received
Jan 19,2022 - Adewale Adekoya has received an email reply from GMC
...
Root Cause(s)
Alerting from Slack (GMC Sync) & on MS Teams (Connections failure)
Logs show failed Web Service requests
...
Action Items | Owner |
|---|---|
Make it simpler to re-run the synchronised job. https://hee-tis.atlassian.net/browse/TIS21-2437 | |
Add documentation on re-running a failed synchronisation (project README) | DONE Joseph (Pepe) Kelly https://github.com/Health-Education-England/TIS-GMC-CLIENT/pull/37 |
...
Lessons Learned
GMC response to our query took a longer time than expected. We need have mulitple contacts in GMC that can handle technical queries.