Skip to main content

Error index

Find the reference page for any DALP error id by its code range, then read its cause, its fix and its retry flag.

Find the range that holds the id in your error, such as DALP-12074, and open that page for the cause, suggested fix, severity and retry flag. The id is in data.id of the error envelope, and in id of an SDK DalpApiError. The code field, such as INDEXER_BARRIER_TIMEOUT, holds the machine name, which the Platform API pages list in their Machine name column. A code that is a name rather than a number, such as DALP-WORKFLOW-FAILED, is on Codes without a number. An error the SDK raises itself, such as sdk.transport.REQUEST_FAILED, has no DALP- id and is not listed here.

Each code is on exactly one page. These ranges have a page in both references, and each of those pages holds different codes: DALP-9000 to DALP-9099, DALP-9200 to DALP-9299, DALP-9300 to DALP-9399, DALP-9500 to DALP-9999. For a code in one of them, search both pages.

Find the page for your error

You have
Read
A smart contract revert
Any other DALP error
A question about retry policy or idempotency
A question about the error envelope and its fields

Branch your integration on the id, the category and the retryable flag in the error envelope, never on the message text. retryable: true, shown as Yes in the Retryable column, means the same request can succeed later without a change to the request. retryable: false means sending it again does not succeed until you act on the suggested fix. Error handling sets the retry policy.

Platform API errors

The Platform API error reference covers the 1,138 errors the Platform API routes return, on these pages:

Contract errors

The contract error reference covers the 814 errors of DALP smart contracts and their deployment, on these pages:

For retry policy, severity and escalation, read Error handling.

Was this page helpful?