Delays processing "backfill" jobs and incorrect job status

[Beneficiary Claims Data API (BCDA) Community]

Hi BCDA Community,

Several of you have reported issues after making job requests with jobs getting "stuck", showing In-Progress: 0%. The BCDA team has identified two underlying issues which we are working to resolve.

1. The x-progress header in the job status response is not being calculated as expected, showing "In-Progress: 0%" until the job completes, is cancelled, or fails.
2. "Backfill" requests (requests without the _since parameter) are taking longer than expected as they approach completion. The BCDA team can confirm these jobs are processing, but are taking longer than expected. The "In-Progress: 0%" bug above makes it appear these jobs have never started.

We sincerely apologize for these issues and the confusion the "In-Progress: 0%" bug has caused with these longer running jobs. We will first work to improve the time to complete job requests without the _since parameter (#2) before we turn our attention to the "In-Progress: 0%" bug.

Please let us know if you have any questions and thanks for your patience as we address these issues.

The BCDA Team

[Beneficiary Claims Data API (BCDA) Community]

Hi BCDA Community,

Today's BCDA release resolves the bug causing the X-Progress response header to always display "In Progress: (0%)" until the job completes, is cancelled, or fails. Now, when you make a request for the status of a job, BCDA will return an X-Progress header like "In Progress: (N%)" where N is a value between 0% and 100% indicating the percentage complete.

For example, if BCDA has started processing your requested job and is about one third complete, you would receive a response header like:

X-Progress: "In Progress: (33%)"

Please let us know if you have any questions about this fix!
The BCDA Team