Thank you very much for the response, but I want to clarify. I was using the polling job status API call, and it was providing wrong, or outdated information.  @Amit_Jain wrote: So the steps you followed are: enqueued the job and got following response: {"requestId":"c0f3#173de0fc479","result":[{"exportId":"f49eb72e-6554-42a6-aba9-260c27890309","format":"CSV","status":"Created","createdAt":"2020-08-11T14:38:27Z"}],"success":true}  You again tried to enqueue job and got following response: {"requestId":"17a7c#173de129713","success":false,"errors":[{"code":"1029","message":"Export 'f49eb72e-6554-42a6-aba9-260c27890309' is in Processing status"}]} You tried to get the status again and it said "Created"  You again tried to enqueue it again and got "is in Completed status"  I was polling "Job Status" in between each Queue call.  1.) Enqueue Job and got a successful response.  2.) A moment later check "status via  /bulk/v1/leads/export/{exportId}/status.json​ This Check status showed the Job to be in "created status"  Since I was worried that my Enqueue job API call did not go through, I tried to enqueue again.  When I would try to queue the job a 2nd time I would get an "error" but I would also get accurate status updates It seems like for some reason Job Status is updating is being lagged or delayed.  TLDR: When a job is enqueued, polling the status of the Job provides inaccurate information. Trying to enqueue the job again will provide an error, but will give accurate status along with the error.    ... View more