When building a BULK API extraction job, I run into conflicting responses to the status of the job. When I first built the job, the enqueued it I followed up with a simple check status and got this response. {"requestId":"c0f3#173de0fc479","result":[{"exportId":"f49eb72e-6554-42a6-aba9-260c27890309","format":"CSV","status":"Created","createdAt":"2020-08-11T14:38:27Z"}],"success":true}
Parsed out to the relevant part: "status": "Created" I was confused, thinking I had already Enqueued this job, so I tried to enqueue it again and I got this (Failed) result.
{"requestId":"17a7c#173de129713","success":false,"errors":[{"code":"1029","message":"Export 'f49eb72e-6554-42a6-aba9-260c27890309' is in Processing status"}]}
Again the Cut down portion to: is in Processing status"}]}
Okay, Strange, I polled the job status again just to see and I got the same response as the first. Telling me the job was in "created" status. I called for the job to enqueue again one last time, this time I told me "is in Completed status" Which is great, I'm going to try to pull the information from it, but why is the job polling telling me the result was successful, but then not telling me the updated job status?
... View more
Customize up to 8 badges at the top of your trophy case for all other Community members to see!
Validate 1
Earned on 2.22.21
Earned by 544 people
Select to learn more
Give Back 1
Earned on 2.08.21
Earned by 2946 people
Select to learn more
Ignite 1
Earned on 2.08.21
Earned by 2958 people
Select to learn more
.png)