Date |
|
Authors | John Simmons (Deactivated) Adewale Adekoya Jayanta Saha Liban Hirey (Unlicensed) |
Status | ImplementingDocumenting |
Summary | Legacy GMC sync failed and Connections showing an error |
Impact | Data in Reval out of date and Admins unable to use Connections |
Non-technical Description
GMC sync failed and subsequently failed to retrieve any doctors
...
Trigger
Unknown change on GMC firewallby the GMC. There was initially a change to the firewall. The continuing problem, with a different way of failing suggests that there was another GMC which also caused an issue.
...
Detection
Slack notification received
...
on inspection of the logs we found this:
...
...
Resolution
TODO: .Contacted GMC as the issue was on their service.
GMC have not elaborated on the cause or resolution
...
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
9, - Sync job ran successfully however no updates from GMC on any changes made on their side
9, - Adewale Adekoya further enquires for any updates from the GMC but no response received
...
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 |
...