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

Benefits Intake API - Claims going expired every time #137

Open
2 tasks done
gwenna97 opened this issue Apr 2, 2020 · 1 comment
Open
2 tasks done

Benefits Intake API - Claims going expired every time #137

gwenna97 opened this issue Apr 2, 2020 · 1 comment

Comments

@gwenna97
Copy link

gwenna97 commented Apr 2, 2020

VA Lighthouse API Bug Report

⚠️ Please read before submitting: As this is a public forum, please do not include any sensitive information (such as your VA API OAuth Client ID, VA API OAuth Client Secret, VA API key, Name, Address, Phone Number, Social Security Number, Medical Record Number, etc). For test apps, please make sure you are using your registered redirect URL, not the URL provided in the example.

Benefits Intake API V1
MicroPact
Production
Claims going expired every time
Multiple clients

Severity of the issue

  • Medium severity: Not blocking work, but needs attention

  • I was able to use the API, but am not getting the results I expected

    <!-- The only workaround is to file the claim manually and not use API -->
    
  1. Submitting some claims electronically

Actual Outcome:

Goes pending then expired every time

Only happening for a some claims

Expected Outcome:

Claim is under 100 MB per document limit
Claim is under 5 GB per submission limit
Should be going electronically without expiration

@ryanlink
Copy link
Contributor

ryanlink commented Apr 2, 2020

Hi Gwenna -

The expired status means that no submission was uploaded (PUT) within 15 minutes to the location created in the initial POST request.

This can happen for several reasons including dropped connections. Your logs may be able to tell you what happened with the upload, and we recommend logic in your code to retry an upload to the same GUID within the 15-minute window if you get anything other than a 200 OK response.

If this is happening consistently, the VA firewall may be terminating connections due to false-positive threat detection in the binary encoding of your PDFs. This was happening with at least one other consumer of the API. If that is the case, we recommend using base64 encoding instead, which is detailed in https://developer.va.gov/explore/benefits/docs/benefits.

Please note when using base64 that the whole payload needs to be encoded, not the individual attachments.

If you or Scott have any further questions, please send an email to [email protected] and we'll get you back on track. Thanks!

Ryan Link
VA Lighthouse Support
developer.va.gov

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants