Troubleshooting Documentation

Troubleshoot Batch Export Skips and Failures

Learn what it means when bulk export skips tickets, fails on some rows, or refuses to start, and how to fix the most common causes.

Troubleshoot Batch Export Skips and Failures

In this doc

batch export troubleshooting Zendesk to Notion skipped tickets bulk export failed tickets

Batch export does not fail in only one way.

A run can:

  • refuse to start
  • partially succeed
  • skip some tickets
  • fail on specific rows

The important thing is to read the result correctly before changing anything.

When export will not start at all

The most common startup blockers are:

  • no usable Zendesk tab is open
  • Notion is not connected
  • no Notion database is selected
  • free export quota has been exhausted for the day

If the extension says it cannot find a usable Zendesk tab, open Zendesk in the current browser window and refresh the page before trying again.

What “skipped” means

A skipped ticket is not necessarily a failure.

It usually means:

  • the ticket already exists in Notion
  • your existing-ticket behavior is set to Skip

In that case, the exporter detected the duplicate and intentionally did not create a new page.

If you expected a fresh export, change the behavior to Replace or Add New first.

What “failed” usually means

Failed tickets are different. These require action.

The most common causes are:

  • required Notion database properties are missing
  • a property exists but has the wrong type
  • Ticket Type in Notion is missing the value used by Zendesk
  • Notion or Zendesk data for that ticket is incomplete or malformed

The bulk export page shows failures ticket by ticket so you can identify whether the issue is global or limited to specific tickets.

Check your Notion database first

Many batch failures come from database configuration, not the batch workflow itself.

Verify that your database includes:

  • Status as Select
  • Tags as Multi-select
  • Last Updated as Date
  • Ticket Type as Select

Also make sure the Ticket Type property already contains the values used in your Zendesk instance, such as Question, Incident, Problem, or Task.

Batch export from saved views: what to verify

If the issue happens only when exporting saved views, check these points:

  • the selected view actually has tickets
  • you loaded the correct page of results
  • the selected ticket count matches what you intended
  • the current Zendesk session still has access to that view

The extension filters out empty views when loading saved views, so if a view does not appear at all, it may currently have zero tickets.

Partial success is normal in real workflows

In bulk export, it is normal for a run to contain both successes and failures.

That is why the extension splits results into:

  • successful exports
  • failed exports

Use that split to decide whether the issue is:

  • a single bad ticket
  • a missing property in Notion
  • a setup issue affecting the entire run

When to cancel and retry

Cancel the run and fix setup first if:

  • almost every ticket is failing
  • you see the same property error repeatedly
  • the wrong database is selected

Retry immediately if:

  • only one or two tickets failed
  • the rest of the run completed as expected
  • you already know the root cause and fixed it

A practical troubleshooting order

Use this order to debug fast:

  1. Confirm Zendesk is open and usable in the current browser
  2. Confirm Notion is connected
  3. Confirm the selected database is the intended one
  4. Confirm required properties and Ticket Type options exist
  5. Check whether skipped tickets are expected based on duplicate handling

That sequence catches most real-world batch export issues without guesswork.