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 4 Next »

Date

Authors

Status

Working on it

Summary

  • Ran the GMC SYNC ETL and INTREPID REVAL ETLs (intrepid-reval-etl  and intrepid-reval-etl-all-prod)

  • We didn't bother adding monitoring to the existing sync jobs as new revalidation is soon going to be live

  • Do need to add monitoring to sync jobs and ETLs for new revalidation - https://hee-tis.atlassian.net/browse/TISNEW-3264

Impact

Non-technical summary

Timeline

-09:48 AM

- 10:25 AM

Created ticket and incident page https://hee-tis.atlassian.net/browse/TISNEW-5728

2020-11-18 Reval Legacy/Old GMC Sync

- Between 10:25 and 11:21

Ran the jobs intrepid-reval-etl and intrepid-reval-etl-all-prod

Fixed the refresh of data but difference between the under notice values between TIS legacy/existing reval and GMC Connect

Root Causes

Trigger

  • User reported in Teams Support Channel

Resolution

Detection

  • User reported in Teams Support Channel

Actions

Lessons Learned (Good and Bad)

  • G

  • No labels

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