Authentication Issues

[Andy McLaughlin]

I'm seeing a lot of errors when requesting data from the /Group endpoint. A mix of 401 Invalid Token and 404 Not Found.

After retrying many times, some requests are getting through, but then I'm seeing the same behavior when querying the /jobs/<JobID> endpoint for the job status. 

Anyone else seeing similar behavior? The code I'm using to generate a token and make requests has not changed on my end. The client ID and secret I'm using were generated recently, so shouldn't be expired. I have logging in place to confirm that my outgoing IP address is the correct one, which has been linked to the client ID I'm using.

If it seems like this issue is on my end, please advise with any troubleshooting steps I should take, thanks!

[Schwindt, Adam]

401 Invalid token error starting Sunday.  Saturday it was fine.

--
You received this message because you are subscribed to the Google Groups "Beneficiary Claims Data API (BCDA) Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bc-api+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bc-api/97b16a04-9ff0-4048-9c37-cbfb70020b28n%40googlegroups.com.

This e-mail and any attachments may contain information which is confidential, proprietary, privileged or otherwise protected by law. The information is solely intended for the named addressee (or a person responsible for delivering it to the addressee). If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete it from your computer.

[Mary]

I'm also getting a 401 starting today trying to hit the runout endpoint which has been working fine for the last 6 weeks. Would be good to hear about if this is a known issue/timeline for a fix. Thanks!

[imran zulfiqar]

Hi BCDA Team,

We've been facing issues with invalid tokens in Runout and Normal Data since last Sunday. We still haven't received the 2024 Data, despite your commitment to providing it by February. Please provide us with the current status, as this ongoing issue is causing significant challenges for us.

Thank you
Imran Zulfiqar | DataEngineer

To view this discussion on the web visit https://groups.google.com/d/msgid/bc-api/b486ac07-7a62-4581-818c-96467a34e6fbn%40googlegroups.com.

[MCS(CR_GR)]

Yes getting same error from yesterday till sunday its was fine. 

To view this discussion on the web visit https://groups.google.com/d/msgid/bc-api/b486ac07-7a62-4581-818c-96467a34e6fbn%40googlegroups.com.

[Neil Copeland]

Same here

[Neil Copeland]

Same here, one org seemed to be successful this AM.  I am going to attempt to restart other orgs.

[Beneficiary Claims Data API (BCDA) Community]

Hi folks,

We're sorry for the service disruption starting this past weekend resulting in frequent 401 and 404 responses from BCDA. We've identified the issue and are working to release a fix today.

Thanks for your patience, and as always feel free to reach out with any questions either via Google Groups or directly to the team via bc...@cms.hhs.gov.

Thanks,
The BCDA Team

[Beneficiary Claims Data API (BCDA) Community]

Hi folks,

We've resolved the issue resulting in frequent 401 and 404 responses from BCDA.

We found that BCDA denied requests intermittently due to a high volume of simultaneous requests.

Due to the change released to resolve the issue, organizations may encounter errors when making a large volume of simultaneous requests from a single IP address. If this occurs, we recommend following an exponential backoff approach in automated requests to BCDA.

Thanks,
The BCDA Team