Date |
|
Authors | |
Status | Documenting |
Summary | Overnight weekend GMC sync failed |
Impact | Data was left unsynchronised on Reval |
Non-technical Description
GMC sync failed - at their end we believe. 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)
Awaiting confirmation.
Action Items
Action Items | Owner |
|---|---|
Lessons Learned
TBC.
Add Comment