This page lists the 51 errors the Platform API can return with a code from DALP-12100 to DALP-12199. 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-12100 | ENS_NOT_CONFIGURED | domain | This deployment resolves no ENS avatars. | The deployment names no ENS network, so no address carries an avatar the platform can fetch. | Ask an operator to configure the ENS network and gateway. The mark still answers the generated disc without this rung. | info | No | 422 |
DALP-12101 | MARK_ | dependency | Mark refresh dependency did not answer. | The avatar store, the ENS resolver, or object storage did not answer, so the platform stored nothing and the mark is unchanged. | Retry the refresh after a short delay. | error | Yes | 503 |
DALP-12103 | party.dependency.FAILED | dependency | Party service temporarily unavailable. | A service the party domain depends on 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-12104 | exec.queue.DEPENDENCY | dependency | Transaction dependency temporarily unavailable. | The transaction request could not read its caller scope or a required queue dependency. | Retry the same request after a short backoff. Do not submit a replacement transaction. | error | Yes | 503 |
DALP-12105 | exec. | dependency | Transaction outcome still unknown. | The transaction may have settled, but the platform could not read its final state. | Read the transaction request status using its transaction id. Do not submit a replacement transaction. | error | No | 503 |
DALP-12106 | portfolio. | dependency | Portfolio write outcome still unknown. | The portfolio write may have reached the chain, but its final outcome could not be read. | Read the transaction request status using its id. Do not submit a replacement write. | error | No | 503 |
DALP-12107 | party. | operational | The party write outcome is unknown. | The queue may have accepted this write, but its final outcome could not be confirmed. | Look up the transaction request before taking further action. Do not submit a replacement write under a new idempotency key. | error | No | 503 |
DALP-12108 | compliance. | operational | The compliance write outcome is unknown. | The queue may have accepted this compliance write, but its final outcome could not be confirmed. | Look up the transaction request before taking further action. Do not submit a replacement write under a new idempotency key. | error | No | 503 |
DALP-12109 | custody. | operational | The smart-wallet write outcome is unknown. | The queue may have accepted this wallet write, but its final outcome could not be confirmed. | Look up the transaction request before taking further action. Do not submit a replacement write under a new idempotency key. | error | No | 503 |
DALP-12110 | PROFILE_ | client | Profile section not found. | No profile section with this id is visible to the active organization; sections owned by another organization answer the same way. | List GET /api/ and retry with an id from that page. | info | No | 404 |
DALP-12112 | PROFILE_ | client | A profile field that holds a value is locked. | Every profile version records which fields held a value. Removing such a field, moving it between on-chain and off-chain storage, changing who fills it, changing its type, dropping one of its choices, or loosening an immutable field would orphan, expose, or invalidate a value an earlier version holds; data.keys lists the locked fields. | Keep those fields as they are, or add a new field with the other settings. | info | No | 409 |
DALP-12113 | PROFILE_ | permission | System profile sections are read-only. | System sections are shared by every organization, so no organization can change them; an organization may only retire one for itself. | Create an organization section with the fields you need instead. | info | No | 403 |
DALP-12114 | ASSET_ | client | The storage or mutability of a metadata field cannot change while deployed tokens use the template. | Tokens deployed from the template already carry metadata under its keys; moving a field between on-chain and off-chain storage would leave one key in both stores, removing an immutable field would orphan a value that cannot change, and loosening an immutable field would let a later write replace a value that was immutable when it was written. data.keys lists the locked fields. | Keep the storage and mutability of those fields as they are, or add a new field under a key no deployed token holds. | info | No | 409 |
DALP-12115 | party. | domain | The created user's identity could not be deployed. | The chain failed the deployment of the created user's identity, so the user was not kept. | Repeat the create with a new Idempotency-Key. | error | No | 409 |
DALP-12116 | party. | dependency | The created user's identity binding could not be read. | The chain did not answer the read that binds the created user's identity, so nothing was deployed and the user was not kept. | Repeat the create with a new Idempotency-Key after a short backoff. | error | Yes | 503 |
DALP-12117 | TOKEN_ | client | The forced transfer's owner {escrowAddress} is a DALP escrow, so the token cannot force-transfer from it. | A DALP escrow tracks its own balances and locks. A token forced transfer out of the escrow address would move its units without updating them, so the platform refuses it before it signs anything. | Move the escrow's units with the escrow add-on's own forced transfer, which keeps its balances and locks right, or pick an owner that is not an escrow. | info | No | 422 |
DALP-12131 | TOKEN_ | domain | The brand logo upload was rejected. | The brand logo upload does not meet the issued-token image rules: the token is external, or the file is not a PNG, JPEG or WebP of at most 5 MB and 2048 px a side, or its stored bytes differ from the declaration. | Upload a PNG, JPEG or WebP of at most 5 MB and 2048 px a side for a token this organization issued, then confirm it with its real size and type. | info | No | 422 |
DALP-12133 | USER_IMAGE_INVALID | client | The profile image upload was rejected. | A rendition is not valid base64, is larger than its byte limit, is not a PNG, or is not exactly 256 px or 64 px square. The platform stored nothing. | Render both renditions as square PNG at 256 px and 64 px, encode them as base64, and send them again. | info | No | 400 |
DALP-12134 | USER_ | dependency | Object storage did not complete the profile image operation. | Object storage did not complete the upload of the profile image renditions. | Restore object storage availability, then send the same image request again. | error | Yes | 503 |
DALP-12136 | auth.apikey.THROTTLED | permission | This API key filled its request window. | This key used its full request allowance for the current window, so the platform did not authenticate the request. | Wait for the key's request window to reopen, then send the request again. | info | Yes | 429 |
DALP-12140 | PROFILE_ | client | An organization section may not take the slug of a system section. | Filled profile fields are recorded as <section slug>., so an organization section whose name derives a system section's slug would shadow it; data.slug names the slug. | Choose a section name that derives a different slug. | info | No | 400 |
DALP-12142 | TOKEN_ | domain | Declared dividends are still unclaimed. | The {{featureName}} feature still owes declared dividends, and detaching or replacing it would leave them on the retired feature. | Let holders claim the declared dividends, or reclaim them, until the feature reports nothing outstanding. Then detach or replace the feature. | info | No | 409 |
DALP-12146 | ORDER_SIGNING_FAILED | dependency | The order was not signed. | The custody provider did not return a signature for the order. Or the order cannot be signed on the platform: the instrument is listed on another chain, the maker is not the wallet that signs for the request, or the maker's signer no longer signs on the platform. | When custody did not answer, sign the order again once the custody provider is available. Otherwise scope the request to the instrument's chain and sign with the maker's own platform signer. | error | Yes | 503 |
DALP-12148 | core. | dependency | A database query failed. | The platform could not complete a database query required for this request. | Retry the request. If the failure continues, contact support with the request id. | error | Yes | 503 |
DALP-12151 | PROFILE_ | client | A profile section a profile version filled cannot be deleted. | A participant holds a value for a field of the section, or a profile version of the organization recorded one, and deleting the section would orphan that value. | Retire the section instead of deleting it; earlier versions keep its values. | info | No | 409 |
DALP-12159 | TOKEN_ | client | The members and links do not form one complete issuance. | The members, structure, templates, or feature links in the request do not form one complete issuance. data.reason names the rule the request broke. | Read data.reason. Send every structure member once with its declared template, or declare every link a standalone member needs, then retry. | info | No | 422 |
DALP-12160 | TOKEN_ | domain | The issuance run conflicts with a newer declaration or an earlier request. | The structure or a template changed after it was reviewed, or the idempotency key already accepted a different declaration. | Reload the structure and templates, review the issuance again, and accept it with a new idempotency key. | info | No | 409 |
DALP-12161 | TOKEN_ | client | The issuance run was not found. | The run does not exist in the active organization and system. | Use the run identifier returned when the issuance was accepted in this organization and system. | info | No | 404 |
DALP-12162 | PARTICIPANT_ | client | Wallet removal refused. | Something still depends on the wallet, and data.reason names what: it still signs for a smart wallet (signs-for-smart-wallet), a custody account that is not archived still uses it (custody-account-open), it still holds a token balance (holds-balance), its holder's identity has a lock-up holder lock on a token of the system that has not reached its unlock time, which an approved wallet's removal through the organisation's managed signer cannot leave behind (holder-locked), its registration is not indexed yet (registration-not-indexed), it sits in an identity registry no organisation resolves (registry-unresolved), the organisation has no managed signer that may unregister it, because none is set up on that chain or it lacks the identity manager role (organization-), another removal of it is running or the wallet is no longer active (removal-in-progress), it changed while it was being removed (wallet-changed), or it is not an EVM wallet of this participant (not-an-evm-wallet). data.subjects names the smart wallets, custody accounts, tokens or registry involved. For every reason except wallet-changed, nothing was submitted; for wallet-changed, the wallet's identity unregistrations may already have been submitted before the archive found the wallet changed. | Resolve what data.reason names, then request the removal again: remove the wallet as a signer, archive the named custody accounts, move the named tokens out, wait for the named tokens' holder lock to reach its unlock time or ask the token's issuer to clear it, or set up the organisation's managed signer on that chain and grant it the identity manager role. For registration-not-indexed and removal-in-progress, wait and retry. | info | No | 409 |
DALP-12163 | CORPORATE_ | domain | This redemption pays its cash leg in the token it burns. | The cash and the burn land in one transaction, so a holder is credited the units the burn destroys and ends the run holding what they started with, while the treasury is short the amount it paid and the record reports the holder as applied. | Name a different asset as the denomination, then confirm again. | info | No | 409 |
DALP-12164 | CORPORATE_ | domain | This redemption's cash leg needs a smart-account executor. | The cash and the burn settle in one smart-account transaction, so a holder is paid and burned together or left untouched. A plain externally owned account sends one call per transaction and has no atomic shape to offer. | Confirm from a smart-account executor, or declare the redemption without a cash leg and settle the payment separately. | info | No | 409 |
DALP-12165 | CORPORATE_ | domain | The maker-checker rules refused this decision. | Maker-checker clears a Corporate Action for execution, and the decision breaks one of its rules: the caller may not decide, the session is impersonated or a machine credential, the caller raised or last previewed this record, a decision already landed on it, the record is not in a decidable state, the plan moved since it was read, the cash leg is not funded, or the approval window closed. The violation in the response names the rule. | Read the named rule. A distinct permitted operator decides from a signed-in session, on a fresh preview when the plan moved and on a funded treasury when the cash leg is short. | info | No | 409 |
DALP-12166 | CORPORATE_ | domain | This redemption prices one or more holders at zero cash. | Cash is floored to whole base units of the denomination asset, so a holder whose units are worth less than one base unit is owed nothing. The cash and the burn land in one transaction, so confirming would destroy those holders' units and pay them nothing. | Raise the price per unit, or announce an amount that prices above zero for every holder, then confirm again. | info | No | 409 |
DALP-12167 | CORPORATE_ | domain | This redemption's denomination asset was not issued in this system. | The cash leg is paid with a plain ERC-20 transfer inside the burn's own transaction, and the executing smart account does not read what that call returned. An asset that reports failure by returning false instead of reverting would leave the burn standing beside a payment that never moved, and only an asset this system issued is known to revert. | Name a denomination asset issued in this system, then confirm again. | info | No | 409 |
DALP-12168 | CORPORATE_ | domain | This token charges a burn fee, so the cash leg cannot be priced. | A burn fee splits every redeemed amount into a transfer to the fee recipient and a smaller net burn. Cash priced on the announced amount therefore pays for units that stay outstanding in the fee recipient's balance, and those units can be redeemed a second time. | Set this token's burn fee to zero, then confirm again. A redemption that declares no cash leg is unaffected. | info | No | 409 |
DALP-12171 | CORPORATE_ | domain | This Corporate Action's election window is closed. | Holder elections are accepted only while the Corporate Action is previewed or approved and its election deadline is open. | Submit the election before the deadline, or use a new Corporate Action. | info | No | 409 |
DALP-12172 | CORPORATE_ | domain | The election choice is not offered by this Corporate Action. | The submitted choice is not one of the options configured for this Corporate Action. | Read the Corporate Action and submit one of its configured choices. | info | No | 409 |
DALP-12173 | CORPORATE_ | domain | The holder is not eligible to elect on this Corporate Action. | The holder was not present in the Corporate Action's record-date eligibility set. | Submit an election only from an eligible holder account. | info | No | 409 |
DALP-12174 | CORPORATE_ | domain | The holder wallet is not authorized to submit this election. | The authenticated wallet does not match the holder wallet authorized for the election. | Retry from the holder's authorized wallet. | info | No | 409 |
DALP-12175 | CORPORATE_ | domain | The election deadline does not permit submission. | The configured election deadline is not in the future. | Set an election deadline after now. | info | No | 409 |
DALP-12176 | CORPORATE_ | domain | The Corporate Action election configuration cannot be used. | The election options or their settlement terms do not form a valid Corporate Action election. | Correct the election configuration and create the Corporate Action again. | info | No | 409 |
DALP-12177 | CORPORATE_ | domain | The Corporate Action's election deadline is still open. | Execution must wait until holders can no longer change their elections. | Wait until the configured election deadline has passed, then confirm again. | info | Yes | 409 |
DALP-12178 | CORPORATE_ | domain | The Corporate Action's election window is locked. | Preview cannot be changed after the election deadline or after a holder has submitted an election. | Create a new Corporate Action or use the stored election outcome. | info | No | 409 |
DALP-12179 | CORPORATE_ | domain | This Corporate Action has no holder-election configuration. | The election route applies only to Corporate Actions created with holder-election terms. | Read the Corporate Action and use its supported operation, or create one with an election configuration. | info | No | 409 |
DALP-12180 | CORPORATE_ | domain | A partial redemption cannot be recorded on a matured bond. | After maturity holders redeem their own tokens at face value, so a partial redemption that burns tokens without paying for them removes a holder's claim. | Let holders redeem their own tokens, or use the maturity redemption of this bond. | info | No | 409 |
DALP-12181 | CORPORATE_ | domain | A spin-off or tradable rights issue requires a child token with the same decimals as the parent. | The child token holds a different number of decimals than the token the holder book was taken from, so every allocation would be the wrong size. | Use a child token with the same decimals as the parent, or create one, then preview again. | info | No | 409 |
DALP-12182 | CORPORATE_ | domain | No holder outside the treasury is entitled to a payment at the record date. | The treasury takes no payment, and at the record date no other eligible holder held enough units to receive one, so the snapshot has no holder to pay. | If the message says no unclaimed entitlement is left to push, every holder is already paid and nothing is left to do. Otherwise cancel this dividend and declare a new one with a later record date or a larger amount, or abort the Corporate Action run. | info | No | 409 |
DALP-12193 | TOO_MANY_REQUESTS | client | Too many requests for this operation. | The caller exceeded a rate or attempt limit on this operation. The refusing limit publishes no error entry of its own, so this general 429 stands in for it. | Wait before retrying. Honour a Retry-After header when the response carries one. | info | Yes | 429 |
DALP-12194 | BAD_GATEWAY | dependency | A service this request depends on returned an answer the platform could not use. | A service this operation depends on answered, but the platform could not use the answer. The failing dependency publishes no error entry of its own, so this general 502 stands in for it. | Retry after a short delay. If it continues, contact support with the request id. | error | Yes | 502 |
DALP-12195 | PRIMARY_ | client | Choose a primary custody account for this participant and network. | The acting participant has no usable primary custody account for this organization and network. No other account is substituted, even if one is eligible. | Choose a primary custody account in this network, or explicitly select one for this request. | info | No | 409 |
DALP-12196 | CUSTODY_ | client | The selected custody account is not eligible for this request. | The selected account is not available to the acting participant in this organisation and network, or is not active and eligible for the request. No other account was substituted. A portfolio read also answers this way when no enabled EVM network in the catalogue is deployed on the requested chain. | Select an active eligible account from this participant's custody-account list for this organization and network. | info | No | 409 |
The previous page is DALP-12000 to DALP-12099. The next page is DALP-12200 to DALP-12299.