404 Jobs Cancelled

[Anthony Haddad]

Hi there,

I am with Oracle Health, I help manage a BCDA data for a client.  Out of the 22 BCDA sources we are pulling data for, there is about 11 that seem to be having issues.  The Jobs are kicked off and return a 200 and 202 response.  But when I query the Jobs for status I am getting a 404 response with a body text mentioning that the job was cancelled.  I have tried both the normal /patient endpoint and runout endpoint.

This behavior is also happening with varying different _since time dates, so I do not believe it is an issue of volume of data.  Help identifying and resolving this issue would greatly be appreciated.  Our client has been without data from these 11 sources since the middle of December.  I had previously made a post, but it never seemed to actually post to the Group.

Thank you, 

Anthony Haddad

[Anthony Haddad]

To whom it may concern,

I believe that I am still seeing this issue with no reply almost a month later.  Our client is getting extremely frustrated with the missing data.  Additionally I have found that the incorrect HTTP response seems be sent on some occasions, specifically when too many requests hit the server.

When too many requests hit the server on an export call a 200 response is being sent (with a JSON body that mentions there is an error).  Would it not be more appropriate to respond with a 429 (Too Many Requests) error when your service decides to throttle an IP?  This type of issue seems to also be part of the problem with my original issue.  When a job is cancelled a 202 response is being returned. This is just a generic "Accepted," response, but if the job is cancelled on the CMS side more clear status codes would help with troubleshooting.