How to Resolve Export Items Stuck in the Export Queue

This article explains why Export Items can stay in the Queued tab even though you sent successful item updates and a completed job event. In some cases the items also return in a new pending Export Job when you export them again. The article also shows how to resolve the problem.

The Symptom

You processed an Export Job, and Pleo accepted every call:

PUT /v3/export-jobs/{jobId}/items returned 200 with "errors": [], and every item was successful.
POST /v3/export-job-events with completed returned 204.
GET /v3/export-jobs/{jobId} shows the job as completed.

However, in the Pleo Web App the expenses are still in the Queued tab and not in the Exported tab. If you export them again from the UI, a new pending Export Job appears in GET /v3/export-jobs. It contains the same accounting entries.

Why This Happens

An Export Job and its items must move through the full sequence, in order. If you skip a step, the entries can stay in the Export queue. The step that is skipped most often is marking each item in_progress before you mark it successful.

How to Reproduce on Staging

In the Pleo Web App, export two expenses.
Send POST /v3/export-job-events with "event": "started" for the new pending job.
Send PUT /v3/export-jobs/{jobId}/items with "status": "successful" for both items. Do not send in_progress first.
Send POST /v3/export-job-events with "event": "completed".
In the Pleo Web App, the expenses stay in the Queued tab.

How to Resolve It

Process each Export Job in this order. Do not skip step 2. If you do, the expenses stay in the Queued tab, even though Pleo accepts every call.

Step	Intent	Event	Status	API Request
1	Start the job	`started`	Job becomes `in_progress`	`POST /v3/export-job-events`
2	Mark every item as being processed	None	Items become `in_progress`	`PUT /v3/export-jobs/{jobId}/items`
3	Report the result for each item after processing	None	Items become `successful` or `failed`	`PUT /v3/export-jobs/{jobId}/items`
4	Finish the job	`completed`, `completed_with_errors` if some items failed, or `failed` if all items failed	Job becomes `completed`, `completed_with_errors` or `failed`	`POST /v3/export-job-events`

Send step 4 only after Pleo has acknowledged every item update from step 3.

1. Mark the Job In Progress

API Endpoint: POST /v3/export-job-events

OAuth 2.0
API Key

curl -X POST "https://external.staging.pleo.io/v3/export-job-events" \
  -H "Authorization: Bearer <access_token>" \
  -H "Content-Type: application/json" \
  -d '{
        "jobId": "8eb648ab-464b-42a0-ba17-eda703657e33",
        "event": "started"
      }'

curl --request POST \
  -u "pls_1ab2cd3e4f5g6h7a89b012c34de56f78_gabc90:" \
  -H "Accept: application/json;charset=UTF-8" \
  -H "Content-Type: application/json" \
  "https://external.staging.pleo.io/v3/export-job-events" \
  -d '{
        "jobId": "8eb648ab-464b-42a0-ba17-eda703657e33",
        "event": "started"
      }'

The response is 204, and the job’s status becomes in_progress.

2. Mark Every Item In Progress

API Endpoint: PUT /v3/export-jobs/{jobId}/items Send every accounting entry in the job with "status": "in_progress", in batches of up to 100 items. Each item needs only accountingEntryId and status.

OAuth 2.0
API Key

curl -X PUT "https://external.staging.pleo.io/v3/export-jobs/8eb648ab-464b-42a0-ba17-eda703657e33/items" \
  -H "Authorization: Bearer <access_token>" \
  -H "Content-Type: application/json" \
  -d '
  [
    { "accountingEntryId": "59540ed2-0d68-4e36-9e31-58223975d9e9", "status": "in_progress" },
    { "accountingEntryId": "6678bcee-c6a4-4b49-bb1e-8f9fd653d16c", "status": "in_progress" }
  ]'

curl --request PUT \
  -u "pls_1ab2cd3e4f5g6h7a89b012c34de56f78_gabc90:" \
  -H "Accept: application/json;charset=UTF-8" \
  -H "Content-Type: application/json" \
  "https://external.staging.pleo.io/v3/export-jobs/8eb648ab-464b-42a0-ba17-eda703657e33/items" \
  -d '
[
  { "accountingEntryId": "59540ed2-0d68-4e36-9e31-58223975d9e9", "status": "in_progress" },
  { "accountingEntryId": "6678bcee-c6a4-4b49-bb1e-8f9fd653d16c", "status": "in_progress" }
]'

3. Mark Each Item Successful or Failed

API Endpoint: PUT /v3/export-jobs/{jobId}/items After your AS/ERP has processed the items, report the result for each one. For the full payloads, including failures, see How to Update Export Items.

OAuth 2.0
API Key

curl -X PUT "https://external.staging.pleo.io/v3/export-jobs/8eb648ab-464b-42a0-ba17-eda703657e33/items" \
  -H "Authorization: Bearer <access_token>" \
  -H "Content-Type: application/json" \
  -d '
  [
    {
      "accountingEntryId": "59540ed2-0d68-4e36-9e31-58223975d9e9",
      "status": "successful",
      "exportedAt": "2026-04-22T10:08:56Z",
      "externalId": "ext-1234",
      "externalUrl": "ext-url"
    },
    {
      "accountingEntryId": "6678bcee-c6a4-4b49-bb1e-8f9fd653d16c",
      "status": "successful",
      "exportedAt": "2026-04-22T10:08:56Z",
      "externalId": "ext-5678",
      "externalUrl": "ext-url"
    }
  ]'

curl --request PUT \
  -u "pls_1ab2cd3e4f5g6h7a89b012c34de56f78_gabc90:" \
  -H "Accept: application/json;charset=UTF-8" \
  -H "Content-Type: application/json" \
  "https://external.staging.pleo.io/v3/export-jobs/8eb648ab-464b-42a0-ba17-eda703657e33/items" \
  -d '
[
  {
    "accountingEntryId": "59540ed2-0d68-4e36-9e31-58223975d9e9",
    "status": "successful",
    "exportedAt": "2026-04-22T10:08:56Z",
    "externalId": "ext-1234",
    "externalUrl": "ext-url"
  },
  {
    "accountingEntryId": "6678bcee-c6a4-4b49-bb1e-8f9fd653d16c",
    "status": "successful",
    "exportedAt": "2026-04-22T10:08:56Z",
    "externalId": "ext-5678",
    "externalUrl": "ext-url"
  }
]'

4. Complete the Job

API Endpoint: POST /v3/export-job-events Send completed if all items succeeded, completed_with_errors if some items failed, or failed if all items failed. For more detail, see How to Update and Complete an Export Job.

OAuth 2.0
API Key

curl -X POST "https://external.staging.pleo.io/v3/export-job-events" \
  -H "Authorization: Bearer <access_token>" \
  -H "Content-Type: application/json" \
  -d '{
        "jobId": "8eb648ab-464b-42a0-ba17-eda703657e33",
        "event": "completed"
      }'

curl --request POST \
  -u "pls_1ab2cd3e4f5g6h7a89b012c34de56f78_gabc90:" \
  -H "Accept: application/json;charset=UTF-8" \
  -H "Content-Type: application/json" \
  "https://external.staging.pleo.io/v3/export-job-events" \
  -d '{
        "jobId": "8eb648ab-464b-42a0-ba17-eda703657e33",
        "event": "completed"
      }'

After Resolving

Check the job and its items:

GET /v3/export-jobs/{jobId} shows "status": "completed".
GET /v3/export-jobs/{jobId}/items shows each item as successful, with exportedAt set.
Refresh the Export page in the Pleo Web App. The expenses move from the Queued tab to the Exported tab.

Get Started

Integration Design

Workflow Guides

How-to's

How to Resolve Export Items Stuck in the Export Queue

The Symptom

Why This Happens

How to Reproduce on Staging

How to Resolve It

1. Mark the Job In Progress

2. Mark Every Item In Progress

3. Mark Each Item Successful or Failed

4. Complete the Job

After Resolving

​The Symptom

​Why This Happens

​How to Reproduce on Staging

​How to Resolve It

​1. Mark the Job In Progress

​2. Mark Every Item In Progress

​3. Mark Each Item Successful or Failed

​4. Complete the Job

​After Resolving

​Related Reading

The Symptom

Why This Happens

How to Reproduce on Staging

How to Resolve It

1. Mark the Job In Progress

2. Mark Every Item In Progress

3. Mark Each Item Successful or Failed

4. Complete the Job

After Resolving

Related Reading