BUG REPORT - Persistent 500 Error on Pagination Index "-10" for ExplanationOfBenefit NDJSON Files

[Jake Halpert]

 Hi DPC API Team,

 We are submitting a formal bug report regarding a persistent failure pattern we have observed over several weeks. This issue affects our ability to retrieve complete EOB datasets when the result set is large enough to require pagination beyond 10 files.

 Summary of the Issue

When the server splits a large EOB query result into multiple paginated NDJSON files, the download consistently fails for the 11th file (suffix -10).

While files with suffixes -0 through -9 are generated and downloaded successfully, requests for the file ending in -10 invariably return a 500 Internal Server Error.

 Observed Behavior

• Successful Downloads: Files [UUID]-0.explanationofbenefit.ndjson through [UUID]-9.explanationofbenefit.ndjson work as expected.
• Failure Point: The file [UUID]-10.explanationofbenefit.ndjson fails to download/retrieve.
• Error Code: HTTP 500 (Internal Server Error).
• Frequency: This pattern is reproducible and has persisted over the last few weeks we believe across all job runs requiring pagination beyond 10 pages.

We appreciate your assistance in resolving this blocking issue.

[Data at the Point of Care (DPC) Community]

Hi Jake,

Thanks for your question regarding the EOB bug. We're reviewing the information you shared and will get back to you shortly.

Thank you,

The DPC API Team

Please be careful not to share either Personally Identifiable Information (PII) as defined in the Privacy Act of 1974 or Protected Health Information (PHI) when communicating with our team via email or in our Google Group. In certain circumstances, CMS may ask you to provide a data file to assist us in troubleshooting a problem that you bring to our attention. In those instances, we will provide you with instructions for how to handle the transmission.

[Data at the Point of Care (DPC) Community]

Hi Jake,

Thanks for flagging this — we’ve identified the underlying issue causing the download failure for files beyond the 10th batch and have implemented a fix.

The fix is expected to be deployed before the end of this week. We expect exports to be processing and downloading normally again by Friday. If there are any delays with the deployment, we’ll be sure to let you know.

Thanks again for your patience, and please reach out if you have any more questions.

Best,

The DPC API Team

Please be careful not to share either Personally Identifiable Information (PII) as defined in the Privacy Act of 1974 or Protected Health Information (PHI) when communicating with our team via email or in our Google Group. In certain circumstances, CMS may ask you to provide a data file to assist us in troubleshooting a problem that you bring to our attention. In those instances, we will provide you with instructions for how to handle the transmission.