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
889 Error #165
Comments
This can also be recreated by using other words followed by a state. All of the following will return the error screen: Some query strings likely return a specific error message, but it appears the site generically displays the error that it could not connect for all errors. |
Looks like errors in the 889 Tool is caused by the data within sam.gov. Tested API in postman and getting the error below. There is currently a warning on the API document page regarding incorrect data (https://open.gsa.gov/api/entity-api/). I was able to recreate the error on successful searches by navigating to different page results. For example if I search "Michigan" it return results, however if I navigate to any result page beyond page 2 I get the same error. |
Great catch. To verify, this is a SAM.gov issue? Hopefully, When they fix it, the 889 tool will return to its normal function. Is that accurate? |
Yes, I believe this is a SAM.gov issue due to the message they are displaying within the api documentation and the fact that some searches return successful but when accessing a different page for the same search errors are being returned. Will continue to monitor SAM.gov for updates and update when issue has been addressed. I believe when they fix the issue the application will run without errors. |
Here are two more vendors that are getting the error message. I did find that I could get to Fisher Scientific if I just search Fisher. Fisher Scientific and Illumina |
A user reported that when they type 'Eastern Michigan" into the the 889 Tool that we get an error message stating, "Sorry, we weren't able to connect to SAM.gov, Please try again later.
The rest of the tool seems to be working - screenshots below.
The text was updated successfully, but these errors were encountered: