This page lists the 78 errors the Platform API can return with a code from DALP-12300 to DALP-12399. Match the id in the error envelope to the DALP Code column, then read Retryable and Suggested Fix. The Platform API error reference explains each column, including Severity, and the DALP error index lists the page for every code range.
DALP Code | Machine name | Category | Message | Why | Suggested Fix | Severity | Retryable | HTTP Status |
|---|---|---|---|---|---|---|---|---|
DALP-12300 | core. | dependency | The blockchain node did not answer. | The blockchain RPC endpoint the network uses did not complete the read this request needs. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12301 | core. | client | No executor network is configured for this chain. | No configured network resolves to the chain the smart-wallet executor was asked to use. | Select a configured chain, or ask an administrator to add the network. | info | No | 404 |
DALP-12302 | core. | operational | Every network for this executor chain is disabled. | The chain the smart-wallet executor was asked to use has configured networks, but all of them are disabled. | Ask an administrator to enable a network for this chain, or select another chain. | error | No | 409 |
DALP-12303 | core. | operational | The platform could not read the executor network's configuration. | The smart-wallet executor's network configuration is unusable: it has no RPC endpoint, its RPC URL is invalid or not HTTP or HTTPS, or its enabled networks name different directory contracts. | Contact support with the X-Request-Id response header so an operator can correct the network configuration. | error | No | 409 |
DALP-12304 | core. | dependency | The executor network's node did not answer. | The RPC endpoint or account factory of the smart-wallet executor's network failed during this request. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12305 | dapi. | client | The request names two networks. | The request carries both X-Chain-Id and X-Network-Id, so it names two networks. | Send only one scope header: X-Chain-Id for an EVM network or X-Network-Id for a Canton network. | info | No | 400 |
DALP-12306 | dapi. | client | The X-Network-Id header is blank. | The X-Network-Id header is present but blank, so it names no platform network. | Send the stable name of the network you want, or omit the header. | info | No | 400 |
DALP-12307 | dapi. | dependency | The organization's network settings are temporarily unavailable. | The platform could not load the organization's network configuration for this request. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12308 | dapi. | client | The X-Custody-Account-Id header is not a custody account identifier. | The X-Custody-Account-Id header value is not a valid custody account identifier. | Send an identifier the custody-account list returns, or omit the header. | info | No | 400 |
DALP-12309 | dapi. | domain | The custody account needs its external wallet to authorize this request. | The selected custody account is controlled by an external wallet, so the platform cannot sign this operation on its behalf. | Prepare the operation, authorize it with the connected wallet, then finalize the signed artifact. | info | No | 409 |
DALP-12310 | dapi. | domain | The external wallet must sign this request. | The selected external custody account has to sign the exact payload the platform prepared for this request. | Connect the selected wallet, sign the returned payload, and send the request again with the signature. | info | No | 409 |
DALP-12311 | dapi. | client | The external wallet signature does not authorize this request. | The external-wallet signature sent with this request does not authorize the prepared signing payload. | Reconnect the selected account and sign the payload returned for this exact request. | info | No | 400 |
DALP-12312 | dapi. | operational | The completed transaction returned no result for this route. | The transaction completed, but the route could not read back the data its response needs. | Read the transaction request to confirm its outcome, then read the resource it changed. Contact support with the X-Request-Id response header if the data stays missing. | error | No | 503 |
DALP-12313 | services. | operational | The organization's submission signer is not bound. | The organization's deployment has no managed signer bound for this system and chain, so the platform cannot submit the operation. | Contact support with the X-Request-Id response header so an operator can repair the organization's signer binding. | error | Yes | 404 |
DALP-12314 | services. | dependency | The organization's submission signer could not be read. | The platform could not read the organization's managed signer binding for this system and chain. | Retry the same operation after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12315 | services. | dependency | The organization's signing provider did not answer. | The organisation's signing provider did not answer, or the bound account, provider or signer key no longer matches the organisation's signer binding. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12316 | services. | operational | The organization's signer does not match its bound wallet. | The wallet the signing provider returns is not the wallet the organization's signer binding records. | Contact support with the X-Request-Id response header so an operator can repair the organization's signer binding. | error | No | 409 |
DALP-12317 | services. | dependency | The transaction processor's dependency did not answer. | A service the transaction processor needs failed while it handled this operation. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12320 | dalp. | domain | The batch cannot proceed. | The batch's payload, chunk sizing, transaction receipt, or token operation state is not valid, so the batch stopped. | Correct the batch payload or the token permissions it needs, then start the batch again. | info | No | 422 |
DALP-12321 | dalp. | client | Workflow not found. | No workflow visible to the caller's organization matches this identifier. | Use the workflow identifier returned to the organization that started it. | info | No | 404 |
DALP-12322 | db. | operational | The custody account store returned an inconsistent result. | The custody account store did not return a row this request requires. | Contact support with the X-Request-Id response header. | error | No | 500 |
DALP-12324 | settlement. | domain | A settlement precondition is not met. | The settlement cannot run the requested operation until one of its preconditions is satisfied. | Satisfy the precondition, then send the request again. | info | No | 422 |
DALP-12325 | settlement. | client | The settlement secret was not accepted. | The settlement secret or its signature failed validation or cryptographic processing. | Send the original secret and a valid signature for this settlement. | info | No | 422 |
DALP-12326 | settlement. | dependency | A settlement dependency is temporarily unavailable. | A service the settlement operation needs did not answer, so the operation did not run. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12328 | settlement. | client | The token-sale document was rejected. | The token-sale document's type, size, visibility, or hash does not meet the upload rules. | Correct the document type, size, visibility, or hash, then upload it again. | info | No | 422 |
DALP-12331 | platform.http.REINDEXING | operational | The indexer is still catching up on this chain. | The indexer for this chain is rebuilding, and the caller asked to be told instead of waiting while it catches up. | Retry after the number of seconds in data.retryAfterSeconds. | info | Yes | 503 |
DALP-12332 | platform. | dependency | Platform asset storage is temporarily unavailable. | The object storage that holds platform assets did not answer. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12334 | dapi. | dependency | The organization's system scope is temporarily unavailable. | The platform could not load the active organization's system and identity registry scope. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12335 | portfolio. | operational | The ballot is waiting on a custody approval. | The platform parked signing this ballot until the custody approval it needs is granted. | Approve the pending custody request, then send the ballot again. | info | No | 409 |
DALP-12336 | dapi. | dependency | The permission check could not run. | The platform could not read what it needs to decide whether the caller may make this request, so the request did not run. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12337 | dapi. | dependency | The token's claim topics are temporarily unavailable. | The store that holds the token's claim topics did not answer, so the request could not complete. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12338 | dapi. | dependency | Pending identity registrations are temporarily unavailable. | The store that holds pending identity registrations did not answer, so the request could not complete. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12340 | dapi. | domain | The token's last administrator cannot be removed. | The change would leave the token without an administrator, so it is refused. | Grant the administrator role to another participant first, then remove this one. | info | No | 409 |
DALP-12341 | dapi. | dependency | The participant for this role change could not be resolved. | The participant, identity or wallet the role change names does not resolve to one participant with wallets this organisation can act on. The message names the cause. | Name a participant or wallet that this organisation holds and that belongs to one participant, then send the role change again. | error | No | 503 |
DALP-12342 | dapi. | client | The role is not one this token grants. | The role in the request is not a role this token's access manager grants. | Send one of the roles the token's access control lists. | info | No | 400 |
DALP-12344 | dapi. | dependency | The token deployment's progress is temporarily unavailable. | The store that records token deployments did not answer, so the deployment's progress could not be read. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12345 | dapi. | client | No token deployment is recorded under this transaction. | No token deployment visible to the caller is recorded under the transaction in the request. | Use the transaction identifier the token create request returned. | info | No | 404 |
DALP-12346 | dapi. | dependency | A token deployment step could not be read. | The platform could not read a step of the token deployment while streaming its progress. | Reconnect to the deployment stream after a short backoff. | error | Yes | 503 |
DALP-12347 | TOKEN_ | dependency | The deployed token could not be read back. | The token was deployed, but its indexed record could not be read back to complete the response. | Send the same request again with the same Idempotency-Key after a short wait. It answers with the deployed token and does not deploy a second one. Without that key, find the token with GET /api/ instead of creating it again. | error | Yes | 503 |
DALP-12353 | dapi. | permission | Setting the token price needs the token's administrator role. | The caller does not hold the role that may set this token's price. | Send the request as a participant with the token's administrator role, or ask one to set the price. | info | No | 403 |
DALP-12354 | dapi. | dependency | The transfer check is temporarily unavailable. | The platform could not simulate the transfer on chain, so it cannot say whether the transfer would succeed. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12355 | dapi. | dependency | The claim could not be issued right now. | A service the claim issuance needs did not answer, so the claim was not issued. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12356 | dapi. | dependency | The conversion feature could not be read. | The platform could not read the conversion feature's on-chain state for this request. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12358 | dapi. | dependency | The denomination token's metadata could not be read. | The denomination contract's symbol() or decimals() call failed, or its answer cannot be read as a symbol and decimals. | Check that the denomination address is an ERC-20 contract that answers symbol() and decimals(), then send the request with a corrected address. | error | No | 503 |
DALP-12360 | dapi. | dependency | The token's access control could not be resolved. | The token implements neither ERC-3643 nor the SMART interface, or it has no access manager, so the platform cannot target this change. | Use a token that implements ERC-3643 or the SMART interface and has an access manager. If the token has both, contact support with the X-Request-Id response header. | error | No | 503 |
DALP-12364 | db. | dependency | The indexer could not read its progress. | The indexer listener could not read its persisted block-progress checkpoint, so the data this route reads is not confirmed current. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
DALP-12365 | platform. | dependency | Platform write outcome still unknown. | The platform write may have been recorded or reached the chain, but its outcome could not be read. | When data.transactionId is present, read that transaction request. When it is absent, no request could be confirmed. For a proposal change, read the proposal before another write. For a role write, read the held roles before another write. Resending the same role set under the same idempotency key reuses the earlier request only while the held roles are unchanged. After they change, it plans only the changes still missing and can open a new request. | error | No | 503 |
DALP-12366 | platform. | contract | A role write failed on chain. | A role write failed on chain. In a role set no earlier write is undone; in a role batch the calls sent before it stay applied on a signing-wallet executor. | Read the transaction request by id and the held roles, then send only the changes still missing. | info | No | 422 |
DALP-12368 | platform. | domain | Another network already serves this chain. | Another enabled network in the catalog already serves this chain id. | Disable or remove the network that serves the chain, or give this network a different chain. | info | No | 409 |
DALP-12369 | platform. | client | The network definition cannot be stored. | The network definition cannot be stored as submitted. | Correct the named field of the network definition, then save it again. | info | No | 400 |
DALP-12370 | dapi. | client | The role expiry is not allowed. | A time-bound role grant must expire at least one minute after the request, and an administrator whose own role expires cannot grant the administrator role. | Send an expiresAt at least one minute in the future, or ask an administrator without an expiry to grant the administrator role. | info | No | 400 |
DALP-12371 | platform. | domain | The network still serves deployed organizations. | Organizations have systems deployed on this chain, and this change would leave the chain without an enabled network. | Keep this network enabled on this chain while those systems are on it. A chain cannot have a second enabled network, so this one must keep serving it. You can still change its RPC endpoints and other settings. | info | No | 409 |
DALP-12372 | platform. | domain | The network still has RPC upstreams configured. | The network's RPC upstreams were checked against its current chain, and this change would move the network to another chain. | Remove the network's RPC upstreams, make the chain change, then add them again. | info | No | 409 |
DALP-12373 | MATURITY_ | domain | This redemption cannot be completed. | The asset is not ready to pay out this redemption, or the redemption transaction reverted. | Contact the issuer of the asset, and redeem again once the issuer confirms the redemption can be paid. | info | No | 409 |
DALP-12374 | RESOLUTION_FAILED | operational | The venue signer is unavailable. | The venue could not read or verify the managed signing identity needed for this operation. | Retry after custody and network services recover. If the problem persists, ask a venue operator to check the signer configuration. | error | Yes | 503 |
DALP-12375 | ORDER_ | domain | The original order is cancelled and its replacement was not placed. | The amendment cancelled the original order, but the replacement could not be placed: a fill of the original had not settled yet, so its remainder stays locked until the venue records that settlement and releases it to the wallet's free venue balance, or the escrow or the book refused the replacement itself. | Repeat the same amendment once the original's remainder is released: the venue places that same replacement and never cancels anything twice. If the repeat is refused again, place a new order. | info | Yes | 409 |
DALP-12377 | platform. | domain | The invitation was already accepted. | This invitation was accepted before, so it cannot be accepted again. | Continue with the organization the invitation already joined, or ask an organization owner for a new invitation. | info | No | 409 |
DALP-12379 | platform. | domain | The invitation has expired. | The invitation passed its expiry date before it was accepted. | Ask an organization owner to send a new invitation. | info | No | 403 |
DALP-12380 | platform. | domain | The invitation is no longer open. | The invitation was canceled or declined, so it can no longer be accepted. | Ask an organization owner to send a new invitation. | info | No | 403 |
DALP-12381 | platform. | domain | The inviting organization is archived. | The organization that sent the invitation is archived and accepts no new members. | Ask the organization's owners to restore it, or accept an invitation from another organization. | info | No | 403 |
DALP-12382 | platform. | domain | The organization already holds this national ID. | The organization already has a member with the same national ID as the invitee. | Ask an organization owner to check the existing member's identity before inviting this person again. | info | No | 409 |
DALP-12383 | platform. | domain | The invitation's roles were never authorized. | The invitation grants on-chain roles that no verified wallet authorized. | Ask an organization owner to authorize the invitation's roles with their wallet, or to send a new invitation. | info | No | 412 |
DALP-12384 | WALLET_ | permission | The step-up challenge does not match this request. | A wallet-verified request redeems a single-use step-up challenge issued to the caller for the active organization, this route, its target, and this exact payload. The request carried none, or one that is unknown, expired, or issued for another request, so the platform stored nothing. | Request a fresh challenge from POST /api/ for this exact request, then send it once with the challenge id in the X-Step-Up-Challenge header. | info | No | 403 |
DALP-12385 | TOKEN_ | domain | The signer refused to sign this claim. | The signer checked the request against custody, authorization, and approval policy and refused it for a reason that will not clear on retry. data.reason names which. | Read data.reason, resolve the named condition (for example, an unauthorized wallet or a rejected approval), then issue the claim again. | info | No | 409 |
DALP-12386 | custody. | client | The wallet signature was not accepted. | The signature in external does not recover to the wallet of the custody account in data.custodyAccountId over the deployment payload this request prepared, or its deadline is no longer current. | Send the request again without a signature to read the current payload, sign that exact payload with the account's connected wallet, then send the fresh signature. | info | No | 400 |
DALP-12387 | custody. | domain | The smart wallet could not be deployed. | A check or step of the deployment refused it, and data.reason names which: account- when the organisation runs no account abstraction on this chain, controller-unauthorized when the wallet's controller is another account or an agent wallet has no mandate validator, factory-missing when no account factory is registered, deadline-expired when the signed deadline passed, deploy-failed when the deployment did not land, wallet-unknown when the participant holds no active smart wallet with this id, or prediction-mismatch when the recorded or factory-predicted address differs from this wallet. | Resolve the reason in data.reason, then send the request again. After an expired deadline, request a fresh payload and sign it. | info | No | 409 |
DALP-12388 | custody. | domain | The smart wallet needs a signature from its controlling wallet. | The custody account in data.custodyAccountId is self custody, so the platform holds no key for it. Its wallet has to sign the account factory payload in data.signingPayload before the smart wallet can be deployed. | Sign data.signingPayload with that account's connected wallet, then send the same request again with the signature in external. | info | No | 409 |
DALP-12389 | party. | domain | This request needs a signature from the selected wallet. | The custody account in data.custodyAccountId is self custody, so the platform holds no key for it. Its wallet has to sign the exact payload in data.signingPayload before this request can continue. | Sign data.signingPayload with that account's connected wallet, then send the same request again with the signature in external. | info | No | 409 |
DALP-12390 | party. | client | The wallet signature was not accepted. | The signature in external does not recover to the wallet of the custody account in data.custodyAccountId, or it covers something other than the payload this request prepared. | Send the request again without a signature to read the current payload, sign that exact payload with the account's connected wallet, then send the fresh signature. | info | No | 400 |
DALP-12391 | CORPORATE_ | domain | This token's instrument does not carry the capital this Corporate Action needs. | Share actions such as a bonus issue need share capital, and capital actions such as a split or a buyback need share or unit capital. The token carries neither capability, or it has the Booked movements feature, which these Corporate Actions do not run on. | Raise this Corporate Action on a share or unit token, or pick a Corporate Action this instrument offers. | info | No | 409 |
DALP-12392 | settlement. | client | The sale's terms documents are fixed. | A terms document can change only while the sale is in setup and its terms hash is not set yet. This sale has left setup, or its terms hash is set or being set, so the terms investors accept can no longer change. | Keep the current terms documents. Other document types still upload and delete as usual. To offer different terms, create a new sale. | info | No | 409 |
DALP-12393 | party. | domain | Identity recovery has run out of attempts. | This user's recovery failed sixteen times, the most attempts the platform runs for one recovery, or the account lifecycle refused to run it. | Contact support with the X-Request-Id response header before starting another recovery. | error | No | 409 |
DALP-12394 | party.recovery.FAILED | domain | Identity recovery stopped before it finished. | A step of this user's recovery failed, so the recovery stopped before it finished. | Read the recovery status for the step that failed, correct its cause, then execute the recovery again to start a new attempt. | error | No | 409 |
DALP-12395 | MULTISIG_ | client | This signer change leaves the wallet unable to reach its threshold. | After the change, the combined weight of the wallet's signers would be below the threshold, so no transaction could collect enough signatures. Nothing was queued. | Lower the threshold first, keep enough signer weight, or add a signer before removing one, then send the change again. | info | No | 422 |
DALP-12396 | MULTISIG_ | client | This address is already a signer of the wallet. | The multisig wallet already counts this address among its signers, so adding it again would change nothing. Nothing was queued. A pending change that already adds this address answers the same way. | Choose a signing key the wallet does not hold yet, then accept the invite again. | info | No | 409 |
DALP-12397 | MULTISIG_ | client | The sender of this invite can no longer change the wallet's signers. | Since the invite was sent, its sender stopped holding a seat or the right to act for the multisig wallet. Nothing was queued and no key was bound. | Ask a current signer of the wallet to send a new invite. | info | No | 409 |
DALP-12398 | WALLET_CHECKER_IS_OWNER | client | A wallet's owner cannot be its own checker. | A checker approves the transactions a wallet's owner starts, so the checker must be another person. The email names the wallet's owner. Nothing changed. | Name another member of this organization as the checker. | info | No | 409 |
DALP-12399 | WALLET_ | client | The checker must be a member of this organization. | No member of this organization signs in with that email, so nobody could approve the wallet's transactions. Nothing changed. | Invite the person to the organization first, or name an existing member as the checker. | info | No | 409 |
The previous page is DALP-12200 to DALP-12299. The next page is DALP-12400 to DALP-12499.