Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate submission bug #103273

Closed
2 tasks
kjduensing opened this issue Feb 18, 2025 · 2 comments
Closed
2 tasks

Investigate submission bug #103273

kjduensing opened this issue Feb 18, 2025 · 2 comments
Assignees

Comments

@kjduensing
Copy link
Contributor

kjduensing commented Feb 18, 2025

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:

  • 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants