You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixing this bug will allow us to communicate that everything is ready in staging. Also it'll make things... work.
Context
When submitting a claim for an appointment, vets-api returns a 400 error. Investigating the logs shows an error message of "Invalid appointment time provided (appointment time cannot be nil)." This appears to happen before the call to the Travel Pay API is made.
We have investigated and fixed:
the non-local time being sent from the frontend
the backend using the non-local time (PR out)
Questions/thoughs:
What we've investigated so far shouldn't give the error message "appointment time is nil". Why is the appt time nil?
Acceptance Criteria
Bug identified
Submission successful
The text was updated successfully, but these errors were encountered:
Purpose
Fixing this bug will allow us to communicate that everything is ready in staging. Also it'll make things... work.
Context
When submitting a claim for an appointment, vets-api returns a 400 error. Investigating the logs shows an error message of "Invalid appointment time provided (appointment time cannot be nil)." This appears to happen before the call to the Travel Pay API is made.
We have investigated and fixed:
Questions/thoughs:
Acceptance Criteria
The text was updated successfully, but these errors were encountered: