Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Summary

Date

Authors

Cai Willis

Status

Resolved (Documenting)

Summary

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-5504

Impact

Revalidation application was functionally unavailable

...

  • This commit solved the datetime issue, but appeared to change the JSON mapping in the application, particularly for REST responsesdocumentation, in such away that it didn’t play well with Camel

...

Action Items

Immediate action

Action Items

Owner

Find an alternative solution for regular expression in integration service

Jayanta Saha

Fix the JSON mapping issue in recommendations, and revert any patchwork done in the FE to compensate

Awaiting outcome of the first action to determine how we proceed on this.

Some mitigation for “accidental” prod triggers - what would this be?

Jayanta Saha

Investigation ticket to be created.Cai Willis

Done

Automated backups or similar “built-in” to the sync process so that it can be aborted and restored as requiredTo determine the value in creating a ticket for this action?

Cai Willis

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-5566

Introduce batch messaging to speed up biggest bottleneck - judging by the work on the overnight doctor sync this could reduce the whole process down to a couple of hours

Already have work lined up in addressing the raised action e.g GMC sync work

...

Lessons Learned

  • Mistakes happen