Bulk API: extracting activities job stuck in Queued status | Community
Skip to main content
A
Anonymous
June 19, 2017
Solved

Bulk API: extracting activities job stuck in Queued status

  • June 19, 2017
  • 4 replies
  • 6519 views

I submitted a bulk API request for retrieving activities 2 days ago. However the status is stuck in "Queued". What should I expect in terms of the processing time, e.g. when it will move from "Queued" to "Processing" and how long the processing itself will take?

Here is a sample curl. You can see it has been 2 days since the job get queued:

$ curl -X GET $MKTO_URL/bulk/v1/activities/export.json -H "authorization: Bearer $MKTO_TOKEN"

{"requestId":"4448#15cc225567f","result":[{"exportId":"e0277059-d03e-4c1c-8546-941632cfce2b","format":"CSV","status":"Queued","createdAt":"2017-06-17T10:03:09Z","queuedAt":"2017-06-17T10:05:28Z"}],"success":true}

$ date -u

Mon Jun 19 21:00:45 UTC 2017

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

    We believe the queued->processing issue has been resolved.  Jobs which were stuck in queued should be getting picked up into processing now.  There's a few other failure types we're seeing and investigating though.

    4 replies

    Kenny_Elkington
    Adobe Employee
    Kenny_ElkingtonAdobe Employee
    Adobe Employee
    June 19, 2017

    Can I assume that you don't also have a bunch of Bulk Leads Jobs queued as well?

    A
    Anonymous
    June 19, 2017

    No. This job is the only job that I queued.

    $ curl -X GET $MKTO_URL/bulk/v1/leads/export.json -H "authorization: Bearer $MKTO_TOKEN"

    {"requestId":"5be3#15cc26d63fd","result":[],"success":true}

    $ curl -X GET $MKTO_URL/bulk/v1/activities/export.json -H "authorization: Bearer $MKTO_TOKEN"

    {"requestId":"45f9#15cc26d3f5d","result":[{"exportId":"e0277059-d03e-4c1c-8546-941632cfce2b","format":"CSV","status":"Queued","createdAt":"2017-06-17T10:03:09Z","queuedAt":"2017-06-17T10:05:28Z"}],"success":true}

    Kenny_Elkington
    Adobe Employee
    Kenny_ElkingtonAdobe Employee
    Adobe Employee
    June 19, 2017

    In that case, I would encourage you to file a support ticket with the details.  Can you get any new jobs to start processing?

    A
    Anonymous
    June 20, 2017

    I'm having the same issue here as well. Let me know if you happen to hear back from support

    A
    Anonymous
    June 20, 2017

    I'm also having the same issue.  Interested to hear what you find.

    Alec_Dibble
    Alec_Dibble
    Level 1
    June 20, 2017

    We are also seeing the same issue. Enqueued 2 jobs yesterday afternoon and they are still in the "Queued" state.

    Kenny_Elkington
    Adobe Employee
    Kenny_ElkingtonAdobe Employee
    Adobe Employee
    June 20, 2017

    We've got an engineering escalation open now and are looking into the issue.

    A
    Anonymous
    June 20, 2017

    I know that you're working on it now, so just an FYI, I'm now seeing jobs processing, but they've been ending in system errors:

    {

    "requestId": "..."

    "result":

     
    {

    "exportId": "..."

    "format": "CSV"

    "status": "Processing"

    "createdAt": "2017-06-20T19:32:23Z"

    "queuedAt": "2017-06-20T19:32:32Z"

    "startedAt": "2017-06-20T19:34:08Z"

    }

     

    {

    "exportId": "..."

    "format": "CSV"

    "status": "Failed"

    "createdAt": "2017-06-20T18:43:00Z"

    "queuedAt": "2017-06-20T18:43:13Z"

    "startedAt": "2017-06-20T18:44:09Z"

    "finishedAt": "2017-06-20T18:49:13Z"

    "errorMsg": "System error"

    }

     

    {

    "exportId": "..."

    "format": "CSV"

    "status": "Failed"

    "createdAt": "2017-06-20T15:46:01Z"

    "queuedAt": "2017-06-20T15:46:12Z"

    "startedAt": "2017-06-20T18:34:16Z"

    "finishedAt": "2017-06-20T18:39:08Z"

    "errorMsg": "System error"

    }

    Kenny_Elkington
    Adobe Employee
    Kenny_ElkingtonAdobe EmployeeAccepted solution
    Adobe Employee
    June 20, 2017

    We believe the queued->processing issue has been resolved.  Jobs which were stuck in queued should be getting picked up into processing now.  There's a few other failure types we're seeing and investigating though.

    Terms & ConditionsAccessibility statement

    Loading footer...