Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Date

Authors

John Simmons (Deactivated)

Status

Documenting

Summary

Overnight weekend GMC sync failed

Impact

Data was left unsynchronised on Reval for half a day

Non-technical Description

GMC sync failed - Due to GMC working on the Service on the Bank Holiday weekend. Data at our end didn’t initially sync. We spotted the problem, re-ran the jobs and all data on Reval is now back up to date.

Trigger

  • Awaiting clarification from GMC.

Detection

  • Monitoring alert on our Slack channel.

Resolution

  • Re-ran the jobs.

Timeline

  • - 01.05: Slack alert that the GMC sync failed.

  • - 08.40: Slack alert that the GMC sync was still failing.

  • - 14.51: GMC sync jobs were re-run successfully.

Root Cause(s)

  • Maintenance on the GMC servers made the unreachable when the ETL ran, after the maintenance was completed we reran the jobs that were then completed successfully.

Action Items

Action Items

Owner

Lessons Learned

  • TBC.

  • No labels

Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213