...
Action Items
Action Items | Owner | Status |
---|---|---|
Why so many placementSpecialties are not found in TISSS sync, triggering another call to TIS sync? Are these for deleted records, if they are in turn not found by TIS sync, or is there a bug / other issue here? | Done | |
Investigate adjusting the cron record-resending job for TISSS sync: either stop it running during the nightly sync job timeframe, run it every 10min instead of every 1min, or determine how to disable it while another job is running | ||
Rerun the sync jobs one by one, confirm success at each step | Done | |
Write tickets to handle record deletions (currently marked with a //TODO) | ||
Contact AWS to determine if there was an issue with SQS Feedback was that there were no particular issues with SQS around the time of the incident, but an open issue on the aws-java-sdk was referenced (https://github.com/aws/aws-sdk-java/issues/2269 ). | Done (Case ID 8876575931) | |
Add ticket to investigate better error handling (e.g. backoff and retry) on SQS message publishing as per Github issue referenced above. |
...
Lessons Learned
Group review for RCA and identifying alternative scenarios is very useful!