429 Error with 0 in retry-after

[Steven Long]

I was implementing the exponential-backoff method suggested but was rate-limited, it seems that the retry-after field in the 429 error header returns a 0 every time. Wondering what the fix here is.

I've tried to re-query the endpoint with no success with wait times incrementing in 20 minutes.

[Beneficiary Claims Data API (BCDA) Community]

Hello!

Sorry for this issue; it seems you've caught a bug in the retry-after header. At this point in time, it should be 300 seconds (5 minutes). We'll make a change to correct this header.

If you are receiving 429 responses from BCDA even after 5 minutes, it may be that your request is duplicating an in-progress job for your model entity rather than making too many HTTP requests. Please check that you are not trying to recreate jobs already marked as "In-Progress.” For reference, you can view both existing and past jobs using the /jobs endpoint. See Request Jobs History for more details, and please note that at this time some jobs are taking longer than normal to process.

Thanks,
The BCDA Team

[Beneficiary Claims Data API (BCDA) Community]

Hello!

We've fixed this bug in the retry-after header and it should now correctly return a value of 300 seconds. Again, we're sorry for this issue. Please reach out if you have any questions or if you need additional support resolving the 429 errors you were receiving previously.

Thanks,
The BCDA Team