Skip to main content
Talk to salesStart

Retry Enrich & Score

Admit a retry for retryable rows in a terminal partial, error, or cancelled Enrich & Score operation.

POST/api/tables/{table_id}/enrich-and-score/{operation_run_id}/retry
HTTP referenceScope tables:read&columns:write&columns:run&companies:write&leads:writeUpdated September 27, 2026

This page documents the canonical HTTP contract for this endpoint.

Only the user who created the parent operation can retry it, and only after its status is partial, error, or cancelled. The service builds a durable retry subset from the original frozen row scope and cell/stage outcomes, excludes completed Fit results, and retries only retryable incomplete work; permanent failures are not retried. It revalidates the original plan, source schema, and rubric, so changed inputs can produce a 409 plan-drift response.

The optional request key is accepted and length-validated, but retry identity/deduplication comes from the persisted retry manifest rather than that field. A successful response admits a durable operation; poll its operation run ID to confirm completion. Developer-key scopes match execute, and the authenticated user must own the parent operation and access the table.

Path parameters

  • table_idrequired

    string

    Table associated with the original operation.

  • operation_run_idrequired

    string

    Parent Enrich & Score operation run to retry.

Body parameters

  • idempotencyKey · optional

    string | null (8-200 characters)

    Optional accepted key (8-200 characters). Retry admission is deduplicated from its persisted retry manifest and row subset.

Definitions

RetryResponse

Returns the same EnrichScoreAdmissionResult shape as execute; queued work must be polled to terminal status.

Fields

  • operationRunId, operation_run_idrequired

    string

    Canonical and compatibility aliases for the new operation run.

  • planRunIdrequired

    string

    Retry plan-run identity.

  • queuedrequired

    boolean

    Whether retry work was queued.

  • title, summaryrequired

    string

    Human-readable receipt details.

  • columns · optional

    object

    Managed columns used by the retry.

RetryResponse example

json
{
  "operationRunId": "oprun_retry_example_01",
  "operation_run_id": "oprun_retry_example_01",
  "planRunId": "planrun_retry_example_01",
  "queued": true,
  "title": "Retry Enrich & Score",
  "summary": "Retry operation queued",
  "columns": {}
}

Errors

StatusMeaning
401Authentication required.
403Caller does not own the operation, cannot access the table, or lacks a required scope.
404Table or parent Enrich & Score operation not found.
409Parent operation is not retryable or a retry is already in progress.
422Invalid retry request.

Docs