VAOS::AppointmentService#put_cancel_appointment - VAMF returning status 500

[grossb1]

As of this 02/10/2021 (02/03/2021-02/10/2021) there were 992 occurrences of this error.

• URL: /var/VeteranAppointmentRequestService/v4/rest/direct-scheduling/site/xxx/patient/ICN/xxx/cancel-appointment

Team will investigate Prometheus, Cloudwatch and the vets-api code-base to determine root-cause of this issue.

Deliverables

• A brief summary of the the results including any data that will help VAMF in identifying the issue.
• Include any supporting documents as attachments (e.g. spreadsheet, etc...).
• A list of any tickets that were opened in Jira.

Notes

• Sentry url with relevant data: http://sentry.vfs.va.gov/organizations/vsp/issues/14995/events/?environment=production&project=3&query=level%3Aerror&statsPeriod=14d
• Example VAMF Responses:

  {
  "id": "8bc68a74-7560-43e8-95dc-f3c31cd2823f",
  "traceId": "b476a4dfa4d8af28",
  "code": 500,
  "message": "Could not cancel appointment from VistA Scheduling Service",
  "errorCode": 7002,
  "detail": "500: {\n  \"code\" : 500,\n  \"message\" : \"70 GENERIC_ERROR:Invalid appointment: APTCCHO^>>> Appointment has a check out date and cannot be cancelled.^1\",\n  \"id\" : \"49c402fb-5913-4fc0-acc6-d999d3776e49\",\n  \"errorCode\" : 500\n}",
  "meta": {
  "upstreamErrorSource": "vista-scheduling-service",
  "upstreamErrorId": "49c402fb-5913-4fc0-acc6-d999d3776e49"
  }
  }

[grossb1]

It looks like this error was incorrectly classified as a 500, a story will be entered by the VOAS backend team to update it to a 409.

Brad Crosby 1 day ago I agree that APTCCHO should result in a 409. I'll get a story in for that. The generic seems like it might actually be an error in VistaLink itself. I'm not sure that warrants a more specific error than a 500. It seems like a pretty exceptional case.

[grossb1]

Associated JIRA ticket: https://issues.mobilehealth.va.gov/browse/VAOSR-1540