Skip to main content
Jason_Ferrell
Jason_Ferrell
Level 2
November 9, 2017
Question

Rest API - Bulk Import Status

  • November 9, 2017
  • 1 reply
  • 6304 views

I'm having an issue tracking the status of bulk imports and I'm curious if anyone else has had the same issue. 

When I create a bulk import and add to a static list, it appears that the batch id that is assigned to the action is the same as the list id.  I think that the bulk import has a queue of up to 10 jobs and can run 2 simultaneously.  However, since all the jobs get the same batchid, when I try to check the progress, I get odd results.  I can generally work around this for large imports that require multiple jobs.  It does create an issue when I try to check the status and it gives me the status of the job from yesterday.

/bulk/v1/leads.json?access_token=123&format=csv&listId=22038&lookupField=email

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Kenny_Elkington
Adobe Employee
Kenny_ElkingtonAdobe Employee
Adobe Employee
November 9, 2017

Do you have any examples demonstrating this?

Jason_Ferrell
Jason_FerrellAuthor
Level 2
November 10, 2017

I'm not exactly sure what you're looking for.  When you upload a CSV to the bulk import using the Rest API link shown above, the result is a JSON object that contains the requestId and three elements of the result:  batchId, importId, and status.  When uploading to a static list, the batchId and the importId are always the same number as the static list id.  For example, above I'm uploading to static list 22038.  When I create upload jobs for this list, both the batchId and the importId are always returned as 22038. 

This causes the status to be imperfect, since I don't get a unique job number for each upload.  There appear to be no parameters in the API to force a unique batchId for this type of upload.

Kenny_Elkington
Adobe Employee
Kenny_ElkingtonAdobe Employee
Adobe Employee
November 13, 2017

Sorry if I was unclear, but I'd like to see some of the example requests and responses where you're observing this behavior, rather than just a description.

Terms & ConditionsAccessibility statement

Loading footer...