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

Version 1 Next »

Date

Authors

Philip Wilsdon (Unlicensed)

Status

In progress

Summary

  1. An issue with matching the outcome correctly

  2. When we don't find the matching outcome we still try to use it fix so the error is at least returned instead of "internal server error

Impact

Bulk upload

Non-technical summary

Reval was showing information that had not been updated from GMC, on further investigation it turned out that the jobs that run overnight to get the data from GMC and then add it into TIS had not run successfully. Once they had been fixed and rerun, Reval showed the correct information.

Timeline

09:40 am

Issue raised in teams, team looking into it

12:44

Initial investigations

  1. Adding UUIDs broken generic upload - already have a fix ready

  2. Trying to use a null outcome when no match found - fix ready

  3. The10.2 outcomes causing issues in bulk upload 

Root Causes

  • G

Trigger

  • A user reported in the team's channel they had issues with bulk upload

Resolution

Detection

  • A user reported in Teams Support Channel

Actions

  • G

Lessons Learned (Good and Bad)

  • Ed

  • No labels

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