List quarantined sync transactions. (admin access required)

Lists transactions the chain sync could not apply. The checkpoint has already advanced past these, so anything still pending is chain state the database has NOT caught up with — some request is running on stale information until it is applied.

get/tx-sync-quarantine

Request

Base URL: ./../api/v1/ (relative, and the document was published on a file host, not at the API’s origin)
URL: ./../api/v1/tx-sync-quarantine
Auth: API key in header token

Query parameters

network'Preprod' | 'Mainnet'

Filter to a single network

paymentSourceIdstring

Filter to a single payment source

status'Unresolved' | 'Pending' | 'NeedsOperator' | 'Resolved' | 'All'

Unresolved: every unapplied entry. Pending: awaiting retry. NeedsOperator: retries exhausted or a non-retryable failure. Resolved: successfully applied or independently confirmed rolled back.

takeinteger

How many entries to return

cursorIdstring

Id of the last entry of the previous page

Response

Quarantine entries

status'success' required

Example response

{
  "status": "success",
  "data": {
    "Quarantine": [
      {
        "id": "quarantine_entry_id",
        "createdAt": "2024-01-01T00:00:00.000Z",
        "updatedAt": "2024-01-01T00:05:00.000Z",
        "txHash": "0000000000000000000000000000000000000000000000000000000000000000",
        "blockHeight": 10000000,
        "txIndex": 3,
        "reason": "ProcessingFailed",
        "attempts": 4,
        "lastError": "Could not decode the datum of output 0",
        "nextRetryAt": "2024-01-01T00:10:00.000Z",
        "resolvedAt": null,
        "needsOperator": true,
        "PaymentSource": {
          "id": "payment_source_id",
          "network": "Preprod",
          "smartContractAddress": "addr_test1..."
        }
      }
    ]
  }
}

Changes

No recorded changes to this operation across all 50 revisions of this API.