Retry a Failed Import

When tracking an import's progress shows a non-zero failed count, or a status of INTERRUPTED, you can re-run just the ids that didn't make it over, without re-processing the ones that already succeeded.

Before You Begin

Make sure you have the request_id of the import you want to retry (or omit it to retry the tenant's most recent import).

Step 1: Send the Retry Request

Send a POST request to the retry endpoint with the request_id as a query parameter.

Endpoint: /api/v1/accounts/crm-import/retry?request_id=<REQUEST_ID>
Headers:
- Authorization: Bearer <TOKEN_THAT_WAS_PROVIDED_BY_CPQ_ADMIN>

Like Start CRM Import, retry is asynchronous: it re-enqueues the failed (and any unfinished) ids and returns immediately:

{
  "request_id": "a1b2c3d4-5e6f-7a8b-9c0d-1e2f3a4b5c6d"
}

The request_id is unchanged, so you continue polling (or listening for the webhook) exactly as before.

Step 2: Poll Status Again

Go back to Get CRM Import Status (same request_id) to watch the re-run progress. Accounts that already succeeded are skipped, so only the previously failed and unfinished ids are reprocessed.

📘
Safe and Idempotent
Retry is a no-op when there is nothing to reprocess, so it's safe to call even if you're not sure whether the import fully succeeded.

❗️
Same Failure Modes Apply
If the underlying cause of the failures hasn't changed (for example, the tenant's CRM integration is no longer supported), retry can fail the same way Start did (400 Unsupported integration: <TYPE>). Check the failure reason values from the status or detail service before retrying to understand whether the issue is likely to resolve on its own (e.g. a rate limit) or needs manual intervention.

📘
Related API Reference
The Retry CRM Import API Reference page documents the endpoint used in this guide.