This page lists the 50 errors the Platform API can return with a code from DALP-14050 to DALP-14099. 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-14050 | CORPORATE_ | domain | This bond has already matured, so it takes no maturity redemption. | The bond already reads as matured on the index or on chain. Its holders can redeem their own tokens, and the bond refuses a second maturity. | Do not record a maturity redemption for this bond. Its holders can already redeem their tokens. | info | No | 409 |
DALP-14051 | TOKEN_ | domain | The {feature} start date is after the chain's current block time. | The {field} value {startDate} is later than the next block's timestamp {blockTimestamp}, both in Unix seconds, and the feature cannot start in the future. | Set {field} to a time at or before the current block time, or leave it out, then attach or replace the feature again. | info | No | 422 |
DALP-14052 | TOKEN_ | domain | The {feature} treasury {treasury} is a token contract, not a wallet. | A token contract cannot pay out the payment currency, so every payout drawn from it reverts. | Pick the wallet that holds the payment currency for {field}, then send the attach, replace or update again. | info | No | 422 |
DALP-14053 | TOKEN_ | domain | Deploying the {feature} feature would revert. | A simulation of the feature factory's createFeature or replaceFeature call reverted, so the attach or replace would fail on chain. | Use errorName and selector, when present, to find the configuration value the feature rejects, correct it, then attach or replace the feature again. | info | No | 422 |
DALP-14054 | ACCOUNT_ | client | The switch to smart wallets cannot start yet. | No network can host smart wallets yet, or a write on the organisation relayer has not finished. Starting now would queue writes that cannot land. | Read data.blocker: add a network that supports smart wallets, or let the writes in data.blockingTransactionIds finish (top up the relayer) or cancel them, then start the switch again. | info | No | 409 |
DALP-14055 | TOKEN_ | domain | A feature {feature} needs is not attached. | {feature} declares other features as dependencies in the feature registry, and the ones listed in missing are not attached to this token. For example dividend yield reads holder balances at the record date, so it needs the historical balances feature. | Attach the features listed in missing first, then attach {feature} again. | info | No | 422 |
DALP-14056 | TRADING_ | client | The announcement was not found. | The announcement id does not name a notice on the selected network that this request can read or withdraw. A notice that was withdrawn in the meantime, and a notice you are not allowed to see or withdraw, answer the same way. | Use an announcement id from the announcements list for the selected network. To withdraw a notice, use a wallet that holds the operator or admin role on the venue it belongs to. | info | No | 404 |
DALP-14057 | TOKEN_ | domain | This feature cannot be replaced. | The Booked movements feature is never replaced, because its lines and their holds would stay on the old instance. | Change the feature's settings through its settings route instead of replacing it. | info | No | 409 |
DALP-14058 | REGISTER_ | domain | The movement could not be acted on. | The token has no Booked movements feature attached, or the movement is no longer waiting for a decision. | List the token's movements, then book or cancel one that is still requested. | info | No | 409 |
DALP-14059 | PRICE_BAND_INVALID | client | The price band is invalid. | A saved configuration must use one price-band mode. Static limits must fit each inheriting instrument's quote-price tick grid exactly. Dynamic bands need a positive reference price that rolls to each official close. A minimum order quantity must be a multiple of the lot size and no larger than the maximum order quantity. A split cannot move an absolute band or push a price below one tick. | Clear the static or the dynamic legacy width, or select a new static or dynamic policy. Use prices on each inheriting instrument's tick grid and a positive rolling reference for dynamic bands. For a split, set the absolute band at the post-split prices in the same change. | info | No | 422 |
DALP-14060 | TRANSACTION_ | client | The transaction queue refused the write's input. | The transaction queue checked the write before sending it and found a field it cannot use, so nothing was sent. | Correct the write's input and send it again. | info | No | 400 |
DALP-14061 | TRANSACTION_ | client | The idempotency key already names a different write. | The transaction queue already holds a write under this idempotency key, and it is not the write in this request. | Send this write under a new idempotency key, or repeat the original write unchanged to read its result. | info | No | 400 |
DALP-14062 | TRANSACTION_ | client | The account that pays for this transaction does not hold enough funds. | The platform checks the paying account's balance before it sends a transaction, so it did not send this one and nothing reached the chain. | Fund the paying account, then try again. If a retry answers that the request already settled, send it as a new request. | info | No | 400 |
DALP-14063 | TRANSACTION_ | client | The idempotency key is retired. | The transaction queue retired this idempotency key before any write carried it, so no write may run under it. | Do not send the write again under this key. Send it under a new idempotency key. | info | No | 400 |
DALP-14064 | TRANSACTION_ | client | The transaction queue holds no transaction the write refers to. | The write refers to a queued transaction the transaction queue has no record of. | Check the transaction the write refers to, or send the write as a new transaction under a new idempotency key. | info | No | 400 |
DALP-14065 | TRANSACTION_ | client | The transaction queue does not run writes for this chain family. | The write names a transaction on a chain family this transaction queue does not drive. | Send the write to the network that serves that chain family. | info | No | 400 |
DALP-14066 | TRANSACTION_ | client | The idempotency key already names a finished transaction. | A transaction under this idempotency key already failed or was cancelled, so the transaction queue did not run it again. | Read the earlier transaction's outcome. To try again, send the write under a new idempotency key. | info | No | 400 |
DALP-14067 | TRANSACTION_ | client | The transaction queue refused the write. | The transaction queue refused the write before sending it, for a reason it does not publish as its own error. The request itself was read correctly. | Check the signing account and the write's idempotency key, then send it again. If it is refused again, contact support with data.requestId. | info | No | 400 |
DALP-14068 | TOKEN_ | client | A token with booked movements needs a register reference and one movement per call. | A token with the booked movements feature books every mint, burn, forced transfer and transfer as one movement, and a booked movement carries a register reference. The call omitted the reference, named several movements, or sent a register reference to a token that does not carry the feature. | Send one movement per call and, for a mint, burn or forced transfer, include registerReference. | info | No | 422 |
DALP-14069 | platform. | domain | No custody provider supports this network. | No healthy managed custody provider enabled for account creation supports this network. | In Organisation settings, open Custody, then Providers. Add missing network coverage, enable account creation, or restore provider health, then retry. | info | No | 409 |
DALP-14070 | CORPORATE_ | domain | This class's dividend must be reclaimed before its money is released; its claim deadline is {claimDeadline}. | The class dividend of this distribution is still open for claims, or its claim deadline has passed and it has not been reclaimed, so its remaining money cannot be released yet. | Wait until the claimDeadline in this response has passed, reclaim the class dividend, then release the class's money. | info | No | 409 |
DALP-14071 | CORPORATE_ | domain | There is nothing left to release for this class. | The class's leg of this distribution holds no money, either because nothing was funded to it or because it was already released. | Read the distribution's recovery state; no release is needed for this class. | info | No | 409 |
DALP-14072 | CORPORATE_ | domain | A completed Corporate Action cannot be aborted. | The run already completed, so there is nothing left to abort. Reversing a completed run is a new action. | Read the record; start a new Corporate Action if the outcome needs reversing. | info | No | 409 |
DALP-14073 | CORPORATE_ | domain | This unpaid holder was already marked paid. | The unpaid holder entry already carries a payment record with who paid, when, and the reference. | Read the unpaid holders list. If the mark is wrong, a governance holder can reopen the entry with a reason and mark it paid again. | info | No | 409 |
DALP-14074 | REDEMPTION_ | domain | The redemption request was not found. | No redemption request with this identifier belongs to your wallets on this token. | List the token's redemption requests and use an identifier from that list. | info | No | 404 |
DALP-14075 | REDEMPTION_ | domain | The holder is not the wallet that signs the request. | A redemption request can only name the wallet that signs it, and the holder in this request is a different wallet. | Leave the holder out, or send the address of the wallet that signs the request. | info | No | 409 |
DALP-14076 | REDEMPTION_ | domain | This token does not take redemption requests. | Redemption requests are open only for fund tokens that can settle a cash buyback and do not use register lines. This token does not meet that rule, or the platform could not read its details. | Send the request for a fund token that meets the rule. If this token should meet it, check its type and features, then try again. | info | No | 409 |
DALP-14077 | REDEMPTION_ | domain | The amount is above the units available to redeem. | The wallet's available units, after its frozen units and the amount held by its open and settling redemption requests on this token, are fewer than the amount in the request. | Send an amount at or below the available units, or cancel an open request to release its units. | info | No | 409 |
DALP-14078 | REDEMPTION_ | domain | The cut-off for this redemption request has passed. | A redemption request can be cancelled only before its cut-off, and the cut-off for this request has passed. | Read the request for its cut-off time. Ask the fund operator to handle a request you cannot cancel. | info | No | 409 |
DALP-14079 | REDEMPTION_ | domain | The redemption request is not open. | Only an open redemption request can be cancelled, and this request has already left the open status. | Read the request to see its status. Create a new request if you still want to redeem. | info | No | 409 |
DALP-14080 | REDEMPTION_ | domain | The idempotency key belongs to a different redemption request. | This key already created a request for another token or another amount, and a key names one request. | Send the new request with a new idempotency key. To read the earlier request, repeat it with the same token and amount. | info | No | 409 |
DALP-14081 | FUND_ | domain | The fund subscription could not be processed. | The token is not a fund without register lines, it has no subscription terms, the request does not exist or is no longer open, the cut-off has passed, the amount, stablecoin or investor does not meet the terms, or a dealing day cannot be settled: the day is not a weekday, no class NAV was published for it, no request is open through it, the class stablecoin cannot price the requests, or the settlement does not execute from the receiving treasury. | Read the token's subscription terms, its subscription requests and the class NAV for that dealing day, then repeat the call with values they allow: settle from the receiving treasury, on a weekday whose NAV is published. | info | No | 409 |
DALP-14082 | PAYMASTER_ | client | The organization has no managed signing binding on this chain. | Reading or rotating the paymaster signer key goes through the organisation's managed custody binding on the paymaster's chain and system. The organisation has none there, or its binding operates another system. | Provision the organization's managed signing binding for this chain's system, then repeat the rotation. | info | No | 422 |
DALP-14083 | PAYMASTER_ | client | The paymaster has no staged custody signer to rotate. | A key rotation promotes a signer that custody has already staged for the paymaster. The paymaster has none staged, and no current signer from which to stage one. | Provision the paymaster signer in custody so the paymaster has a current signer, then repeat the rotation. | info | No | 409 |
DALP-14084 | market- | operational | The feed write's signer checks could not complete. | An indexed token row the feed write depends on does not match its expected shape, or the chain node refuses the feed signer key read as sent, so the write cannot succeed as asked. | Ask an operator to reindex the affected token range or correct the chain node's RPC configuration, then send the write again. If it still fails, contact support with the X-Request-Id response header. | error | No | 500 |
DALP-14085 | reporting. | operational | The report file could not be written. | The platform read the report's data but could not write it in the requested format, for example because the holders exceed what one XLSX worksheet holds. The same request fails the same way. | Do not retry. Request another format, such as CSV, or contact support with the X-Request-Id response header. | error | No | 500 |
DALP-14086 | custody. | operational | Indexed token data validation failed. | An indexed token row the participant wallet read needs does not match its expected shape, so the read cannot succeed as asked. | Reindex the affected token range, then request the read again. If the read still fails, contact support with the X-Request-Id response header. | error | No | 500 |
DALP-14087 | CUSTODY_ | operational | A custody dependency refused the request. | The custody provider, its credentials or the custody store refused a step this request needs, for a reason a retry does not change. | Do not retry. Contact support with the X-Request-Id response header so an operator can correct the custody configuration. | error | No | 500 |
DALP-14088 | reporting. | operational | A reporting dependency refused the request. | Object storage refused a step this request needs, for a reason a retry does not change. | Do not retry. Contact support with the X-Request-Id response header so an operator can restore the stored file. | error | No | 500 |
DALP-14089 | party.dependency.REFUSED | operational | A party dependency refused the request. | A service the party domain depends on refused the request for a reason a retry does not change. | Do not retry. Contact support with the X-Request-Id response header so an operator can correct the cause. | error | No | 500 |
DALP-14090 | compliance. | operational | A KYC dependency refused the request. | Object storage or the secrets store refused a step the KYC route needs, for a reason a retry does not change. data.dependency names the step. | Do not retry. Contact support with the X-Request-Id response header and data.dependency so an operator can correct the cause. | error | No | 500 |
DALP-14091 | exec.secrets.SLOT_FAILED | operational | The signer-key store refused the operation. | The signer-key store refused the operation for a reason that retrying will not change, such as a rejected credential, an invalid store configuration, or a malformed stored value. | Do not retry. Contact support with the X-Request-Id response header so an operator can correct the signer-key store. | error | No | 500 |
DALP-14092 | settlement. | dependency | Settlement write outcome still unknown. | The transaction queue may have accepted the settlement write, but its outcome could not be read. | Read the transaction request status using its id. Do not submit a replacement write. | error | No | 503 |
DALP-14093 | settlement. | operational | The token-sale document store refused the operation. | The document store refused the operation for a reason that retrying will not change, such as a missing object or a store configuration fault. | Do not retry. Contact support with the X-Request-Id response header so an operator can check the document store. | error | No | 500 |
DALP-14094 | ASSET_ | domain | The template's required features are incomplete or conflict: {reason}. | A feature in requiredFeatures depends on a feature the template does not carry, or two carried features cannot run on the same token. data.reason names each feature involved. | Add every named dependency to requiredFeatures, or remove one feature from each conflicting pair, then save or publish the template again. | info | No | 422 |
DALP-14095 | TOKEN_ | domain | A feature configuration value cannot be deployed: {reason}. | Token create encodes each template feature's featureConfigs entry into the deploy call before anything is queued, and one value cannot be encoded or breaks a rule of its feature. data.reason names the feature and the value. | Correct the named value in the matching featureConfigs entry and resubmit the token creation request. | info | No | 422 |
DALP-14096 | REGISTER_LINE_NOT_FOUND | domain | The movement was not found. | No movement with this number is visible to you on this token. | List the token's movements and use a number from that list. | info | No | 404 |
DALP-14097 | REGISTER_ | domain | A subscription request is already open. | A holder can have one open subscription request at a time, and this holder has one that is still waiting. | Wait for the open request to be booked or cancelled, then request again. | info | No | 409 |
DALP-14098 | REDEMPTION_ | domain | The date is not a dealing day. | A fund settles redemption requests only on its dealing days, which are the weekdays from Monday to Friday. The date in this call falls on a Saturday or a Sunday. | Send a date from Monday to Friday. Use the dealing day of the requests you want to settle. | info | No | 409 |
DALP-14099 | REDEMPTION_ | domain | The fund has no usable NAV for this dealing day. | The platform cannot price a unit for this dealing day. The system has no price feed directory, no NAV was published during the dealing day, or the NAV is too low to give a price above zero in the stablecoin's smallest unit. | Publish the fund's NAV for this dealing day to its price feed, then settle again. If the system has no price feed directory, set one up first. | info | No | 409 |
The previous page is DALP-14000 to DALP-14049. The next page is DALP-14100 to DALP-14199.