# DALP-14200 to DALP-14299

Source: https://docs.settlemint.com/docs/api-reference/errors/platform-api-error-reference/dalp-14200-14299
Cause, fix, HTTP status and retry flag for every Platform API error with a code from DALP-14200 to DALP-14299.

This page lists the 64 errors the Platform API can return with a code from DALP-14200 to DALP-14299. Match the `id` in the error envelope to the DALP Code column, then read Retryable and Suggested Fix. The [Platform API error reference](https://docs.settlemint.com/docs/api-reference/errors/platform-api-error-reference#how-to-use-this-reference) explains each column, including Severity, and the [DALP error index](https://docs.settlemint.com/docs/api-reference/errors) lists the page for every code range.

| DALP Code | Machine name | Category | Message | Why | Suggested Fix | Severity | Retryable | HTTP Status |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| DALP-14207 | `WHITELIST_DESTINATION_IN_USE` | domain | This address cannot be added as a withdrawal destination. | This address is already a withdrawal destination, or another entry for it is still in use. | Use one of your existing destinations for this address, or choose another destination. | info | No | 409 |
| DALP-14208 | `WHITELIST_TRANSITION_REFUSED` | domain | The destination entry does not accept this step. | This destination entry does not accept this step in its current state, or the Idempotency-Key it was sent under already named a different entry. A review from the same user who proved the destination is refused too. | Read the entry as it stands and take the step its current state allows. If a reused Idempotency-Key caused the refusal, send the instruction under a key of its own. Ask another operator to review a destination you proved. | info | No | 409 |
| DALP-14209 | `WHITELIST_ENTRY_UNAVAILABLE` | client | The withdrawal destination was not found. | No destination entry matches this identifier for this participant. | Read the participant's own destinations and use one of their identifiers. | info | No | 404 |
| DALP-14210 | `WHITELIST_DESTINATION_PROOF_INVALID` | domain | The destination control proof is invalid. | The signed proof does not match the challenge the platform issued, the challenge expired, is not valid yet or belongs to an earlier custody reset, or the signature is not the destination address's own canonical signature. | Request a fresh challenge and sign the message it answers. | info | No | 422 |
| DALP-14211 | `WHITELIST_DESTINATION_ACTIVE_ELSEWHERE` | domain | The destination is already active on another entry. | This destination is already active on another whitelist entry in this organization, and a destination may be active on one entry at a time. | Refuse this entry, or have the other entry revoked before clearing this one. | info | No | 409 |
| DALP-14218 | `CUSTODY_PROVIDER_UNAVAILABLE` | dependency | The custody provider or the transaction queue is temporarily unavailable. | The custody provider, its authenticated probe, the custody store, the participant directory, the wallet's chain or the transaction queue did not answer in time, so the custody request could not be completed. | Retry the request. If the failure continues, check the custody provider's status and contact support with the request id. | error | Yes | 503 |
| DALP-14219 | `CUSTODY_LIFECYCLE_CONFLICT` | domain | The custody account changed while this lifecycle step was decided. | The custody account's state refuses this step. Another request moved its lifecycle or claimed your first account on this network, an earlier create request has not finished, the account is inactive or still holds something to release, the wallet cannot carry this policy, or the transaction queue rejected the wallet change. | Read the custody account again and take the step its current state allows. | info | No | 409 |
| DALP-14220 | `CUSTODY_WALLET_NOT_FOUND` | client | Wallet not found. | No wallet visible to the caller matches this identifier, or the participant it belongs to is no longer registered. | Refresh the wallet list and choose a wallet returned there. | info | No | 404 |
| DALP-14221 | `MULTISIG_APPROVAL_CONFLICT` | domain | The multisig approval conflicts with the wallet's state. | The approval expired, is bound to a different user operation than the wallet holds, this controller already signed it, it has not collected the weight its threshold needs, or it reached its threshold on a path that cannot execute it yet. | Read the wallet's pending approval and sign the operation it currently holds, once per controller. | info | No | 409 |
| DALP-14222 | `PARTICIPANT_NOT_FOUND` | client | Participant or contact not found. | No participant, or no contact in the caller's contact book, matches this selection in the acting organization. | Use a participant returned by the participant list, or a contact returned by the contact list. | info | No | 404 |
| DALP-14223 | `IDENTITY_NOT_FOUND` | client | Not found in the identity registries. | No identity, claim topic, trusted issuer or identity recovery matches this request in the identity registries. | Check the wallet, topic, issuer or user the request names; create or register it first if it should exist. | info | No | 404 |
| DALP-14224 | `IDENTITY_SCOPE_NOT_FOUND` | client | The identity registry is not available for this organization and chain. | The requested identity scope or registry is not indexed for this organization and chain. | Deploy the system or register the required identity registry for this chain. | info | No | 404 |
| DALP-14225 | `CLAIM_NOT_FOUND` | client | Claim not found. | No claim is recorded for this identity and topic. | Issue the claim before revoking or reading it. | info | No | 404 |
| DALP-14226 | `PARTICIPANT_CONFLICT` | domain | Another participant already holds this key or user link. | Another participant already holds this natural key or user link. | Read the existing participant and continue from it. | info | No | 409 |
| DALP-14227 | `IDENTITY_REGISTRY_CONFLICT` | domain | The identity registry holds a different state than this write assumed. | The identity registry already holds the requested state, or a different state than this write assumed. | Read the registry entry and continue from it, or send a write matching its current state. | info | No | 409 |
| DALP-14228 | `PARTICIPANT_ACCESS_DENIED` | permission | No capability over this participant. | The caller holds no capability over this participant. | Ask a participant manager for the capability, then retry. | info | No | 403 |
| DALP-14229 | `PARTICIPANT_REGISTRATION_INVALID` | client | The registration request is not valid in its current state. | The registration request is not valid in its current state. | Read the registration list and send a request the state allows. | info | No | 400 |
| DALP-14230 | `CLAIM_INVALID` | client | The claim is not valid for its topic. | The claim topic, value or payload is not valid for this topic scheme. | Send a value matching the topic scheme from the topic catalog. | info | No | 400 |
| DALP-14231 | `MULTISIG_DRAFT_INVALID` | client | The multisig draft does not allow this change. | The draft threshold, seat state or member-set version does not allow this change. | Read the draft and send a change its current member set allows. | info | No | 400 |
| DALP-14232 | `RECOVERY_PRECONDITION_FAILED` | client | The recovery preconditions are not met. | The recovery preconditions on the wallet and its target are not met. | Read the recovery preview and satisfy every precondition it lists. | info | No | 400 |
| DALP-14233 | `IDENTITY_SCOPE_CHAIN_UNAVAILABLE` | dependency | The chain backing this identity scope is unavailable. | The chain backing this identity scope is unavailable. | Retry after a short backoff. If it keeps failing, ask an operator to check the RPC endpoint of the network that backs this identity scope. | error | Yes | 503 |
| DALP-14234 | `IDENTITY_SCOPE_DIRECTORY_UNRESOLVED` | dependency | The chain's Directory could not be resolved. | The Directory that publishes this chain's global registries could not be resolved. | Give the chain exactly one enabled network catalog entry naming a Directory, and register the global registry under its key in that Directory. | error | No | 503 |
| DALP-14235 | `CONTACT_DUPLICATE` | client | A contact for this wallet already exists. | This user already keeps a contact for this wallet. | Rename the existing contact instead of adding a second one. | info | No | 409 |
| DALP-14236 | `TRANSACTION_STATE_CONFLICT` | domain | The transaction's state does not allow this transition. | The transaction already finished, holds signed material, sits on a nonce lane that refused the change, or another actor moved it to a new state first. | Read the current transaction state before choosing another operation. | info | No | 409 |
| DALP-14237 | `TRANSACTION_IDEMPOTENCY_KEY_SETTLED` | client | This idempotency key already names a settled transaction. | The idempotency key already names a transaction that has settled. | Use the prior result, or submit a distinct intent with a new idempotency key. | info | No | 409 |
| DALP-14238 | `TRANSACTION_IDEMPOTENCY_KEY_CONFLICT` | client | This idempotency key already names a different write. | The idempotency key already names a different write from this sender on this chain, or its 24-hour matching window has closed. | Submit this write with a new idempotency key; to retry the original write inside its 24-hour window, resend it unchanged. | info | No | 409 |
| DALP-14239 | `TRANSACTION_CANCELLATION_REFUSED` | domain | The transaction cannot be cancelled now. | The transaction is with the signer, and a cancel is refused while it is being signed. | Wait until the transaction request shows the transaction as broadcast, then send the same cancel again. | info | Yes | 409 |
| DALP-14240 | `TRANSACTION_PREPARATION_CLAIM_CONFLICT` | domain | The transaction preparation has another active claim. | Another client holds an active claim on this transaction preparation. | Resume the active claim or wait for its lease to expire. | info | No | 409 |
| DALP-14241 | `TRANSACTION_PREPARATION_PREIMAGE_MISMATCH` | client | The authorization does not match the prepared transaction. | The authorization artifact does not match the canonical preparation preimage. | Authorize the exact canonical preimage returned by the preparation endpoint. | info | No | 409 |
| DALP-14242 | `AA_VALIDATION_FAILED_RETRYABLE` | domain | The user operation failed ERC-4337 validation for a reason that can clear. | The bundler or entry point refused the user operation with an AA code whose cause can clear on its own, such as a nonce or deposit that is not in yet place. | Wait for the cause to clear, such as a nonce or deposit that is not in yet place, then resubmit the same user operation. | info | Yes | 422 |
| DALP-14243 | `AA_VALIDATION_FAILED` | domain | The user operation failed ERC-4337 validation. | The bundler or entry point refused the user operation with an AA code that resubmitting the same operation cannot clear. | Simulate the user operation to read its AA code, correct the factory, account or paymaster the code names, then build a new user operation. | info | No | 422 |
| DALP-14244 | `EXECUTION_FUNDING_REQUIRED` | domain | Execution ended before its paying account was funded. | The account that pays for this execution held too little. The execution waited for funding, and it ended when the pause was declined, a waiting window closed, or its re-broadcasts ran out. | Fund the paying account under Organisation settings, Transaction funding, then send the write again with a new idempotency key. | info | Yes | 422 |
| DALP-14245 | `PAYMASTER_SPONSORSHIP_DENIED` | permission | Paymaster sponsorship was denied. | The paymaster did not sponsor this operation. The organisation's policy refuses it, no sponsorship paymaster covers it on this network, the paymaster signer is unavailable, or the sponsorship ticket expired. | Use an approved sponsor policy, or submit without sponsorship. | info | No | 403 |
| DALP-14246 | `PAYMASTER_NOT_FOUND` | client | No active paymaster matches the request. | No active indexed paymaster matches the request. | Deploy or index the organization paymaster, then retry. | info | No | 404 |
| DALP-14247 | `WALLET_VERIFICATION_SESSION_REQUIRED` | auth | Wallet verification needs a signed-in session. | The operation needs wallet verification, and the request carries no signed-in session that identifies whose wallet to verify. | Sign in again, then retry with a wallet verification proof. | info | No | 401 |
| DALP-14248 | `SETTLEMENT_NOT_FOUND` | domain | Settlement resource not found. | No settlement, settlement leg or token sale visible in the active scope matches this request. | Use a settlement resource returned in the active scope. | info | No | 404 |
| DALP-14249 | `SETTLEMENT_FORBIDDEN` | permission | The acting party may not perform this settlement operation. | The acting participant or wallet is not a party allowed to perform this operation on the settlement. | Act as a participant or wallet that is a party to the settlement with the needed role. | info | No | 403 |
| DALP-14250 | `SETTLEMENT_STATE_CONFLICT` | domain | The settlement's state does not allow this operation. | The settlement is in a state that does not accept this operation, such as executed, cancelled or expired. It also answers an Idempotency-Key reused for a different request, and a sale write that the sale's funding headroom or mint rules refuse. | Read the settlement and use an operation its current state allows, or send a different request under a new Idempotency-Key. | info | No | 409 |
| DALP-14251 | `CANTON_RESOURCE_NOT_FOUND` | client | Canton resource not found. | The Canton resource is absent, or it is not disclosed to the active organization. | Use a Canton resource returned for the active organization. | info | No | 404 |
| DALP-14252 | `CANTON_ALLOCATION_CONFLICT` | domain | The allocation conflicts with an existing intent. | An allocation intent with different immutable input already exists for this request. | Read the existing allocation before creating another intent. | info | No | 409 |
| DALP-14253 | `CANTON_SUBMISSION_CONFLICT` | client | This submission id already names a different submission. | The submission id already holds different immutable input. | Read the existing submission, or send the new one under a new idempotency key. | info | No | 409 |
| DALP-14254 | `VENUE_SIGNER_UNRESOLVABLE` | operational | The venue signer cannot be resolved. | The venue's signing identity could not be resolved, and the failure does not clear on retry. | Ask a venue operator to check the venue's signer configuration in custody, then send the request again. | error | No | 503 |
| DALP-14255 | `VENUE_CONFIGURATION_CONFLICT` | permission | The venue configuration cannot be claimed in this organization. | The venue configuration is held by another organization, so this organization cannot claim it. | Select the organization that owns this venue, or contact an administrator. | info | No | 409 |
| DALP-14256 | `VENUE_FEE_TIER_SCHEDULE_INVALID` | client | The fee tier schedule breaks the ladder rules. | Each tier's threshold must be greater than zero and greater than the one before, its discount must be at least the one before, the ladder holds at most 8 tiers, and the window must be 1 to 365 days. | Correct the ladder so each tier needs more volume and gives at least the same discount as the one before, then submit again. | info | No | 422 |
| DALP-14257 | `VENUE_FEE_TIER_SCHEDULE_CONCURRENT_EDIT` | client | The fee tier schedule changed while this edit was open. | Another edit recorded a newer version of this fee tier schedule after the version this edit started from. | Reload the current fee tier schedule, reapply the change on top of it, and submit the edit again. | info | No | 409 |
| DALP-14258 | `PORTFOLIO_QUERY_REJECTED` | client | The listing query uses a filter the listing does not publish. | A query member did not match the filter vocabulary this listing publishes. | Send an operator and an operand the column publishes, then request the listing again. | info | No | 400 |
| DALP-14259 | `GOVERNANCE_PROPOSAL_PREFLIGHT_FAILED` | domain | The governance action cannot be taken in the proposal's current state. | The governor refuses this proposal or ballot in its current state: the proposal is not open for voting, the caller lacks the voting power or authority it needs, or a timing condition is not met. | Check that the vote is open, that your wallet has the voting power or authority it needs, and that the vote's dates are still valid. Then try again. | info | No | 422 |
| DALP-14260 | `FILING_ACT_REFUSED` | domain | A filing rule refused this act. | A filing lifecycle rule refused the act. `data.refusal` names it: an act the obligation's fulfilment mode never takes, a maker acting as checker, a missing signature, an enterer approving their own entry, an acknowledgement time out of order, unrecorded or refused coverage, a session acting as another user, or validation findings that still stand. | Read `data.refusal`, satisfy that rule, then repeat the act. | info | No | 409 |
| DALP-14261 | `REQUEST_INVALID` | client | The request does not match the route's schema. | A part of the request, its body, query, path or headers, did not match the published schema for this route. | Correct the fields that data.errors names, or check the request against the route schema, then send it again. | info | No | 400 |
| DALP-14262 | `REQUEST_STATE_CONFLICT` | domain | The write collides with state the platform already holds. | The write collided with state the platform already holds, so the platform did not apply it. | Read the current state and continue from it. | info | No | 409 |
| DALP-14263 | `KYC_VERSION_STATE_INVALID` | domain | The KYC version's state does not allow this transition. | The KYC version or action request cannot take this step: its state does not allow it, a new version cannot be created now, or the national id is already used. | Read the KYC version and use a transition its current state permits. | info | No | 409 |
| DALP-14264 | `PROFILE_FIELDS_REFUSED` | client | Some profile fields were refused. | The request names profile or KYC fields the server refused; `data.errors` lists each field and why. | Correct or remove the fields listed in `data.errors`, then send the request again. | info | No | 400 |
| DALP-14265 | `INVALID_REQUEST_NETWORK_IDENTITY` | client | The X-Network-Id header is not a valid network id. | The X-Network-Id header value is not in network-id form. | Send a network id returned by the networks list, or omit the header to use the default network. | info | No | 400 |
| DALP-14266 | `OFF_CHAIN_ORGANIZATION_PERMISSION_REQUIRED` | permission | The organization does not hold the permission this action needs. | The caller's organization role does not grant the off-chain permission this action requires. | Ask an organization owner or administrator for a role that grants it, then retry. | info | No | 403 |
| DALP-14267 | `OFF_CHAIN_USER_PERMISSION_REQUIRED` | permission | The caller does not hold the permission this action needs. | The signed-in user does not hold the off-chain permission this action requires. | Ask an administrator for a role that grants it, then retry. | info | No | 403 |
| DALP-14268 | `REQUEST_CHAIN_CUSTODY_ACCOUNT_REQUIRED` | permission | This action needs a custody account on the requested chain. | The request acts on a chain where the caller has no custody account to act through. | Select or create a custody account on this chain, then retry. | info | No | 403 |
| DALP-14270 | `TRANSACTION_QUEUE_CONFLICT` | domain | The submission collides with one the queue already holds. | The queue timed out waiting for this submission to settle, or an earlier write for the same request is still being processed. A Canton submission also answers this code when its idempotency key already holds different input. | When the message says the key holds different input, send the new submission under a new idempotency key. Otherwise read the existing submission, then send the same request again once it settles. | info | No | 409 |
| DALP-14271 | `TOKEN_FEE_ACCOUNTING_FEATURE_NOT_FOUND` | client | The token has no transaction fee accounting feature. | Fee accounting acts on the token's transaction fee feature, and the token has none attached. | Attach the transaction fee feature to the token before collecting or reading its fees. | info | No | 404 |
| DALP-14272 | `CLAIM_ISSUE_APPROVAL_PENDING` | operational | The claim issue is waiting for an approval. | Issuing this claim waits for an approval that has not been granted yet. | Approve the pending request, then send the claim issue again. | info | Yes | 409 |
| DALP-14273 | `DATABASE_QUERY_REFUSED` | dependency | A database query failed for a reason a retry does not fix. | The platform's database refused a query this request needs, for a reason such as a constraint, a permission or an invalid query, that sending the same request again does not change. | Do not retry the same request. Contact support with the request id. | error | No | 503 |
| DALP-14274 | `DURABLE_EXECUTION_ENGINE_CALL_MALFORMED` | dependency | A workflow engine request or reply did not match its schema. | A request to the workflow execution service, or its reply, failed to encode or decode against its schema, so sending the same request again fails the same way. | Do not retry the same request. Contact support with the request id. | error | No | 503 |
| DALP-14275 | `CUSTODY_CREDENTIALS_TEMPORARILY_UNAVAILABLE` | dependency | Custody credentials for this organization are temporarily unavailable. | The custody provider, its secrets backend or the custody record store did not answer, the provider could not be set up from the stored configuration, or no credential is stored in its secret slot, so the custody operation could not start. | Check the custody provider and secrets backend, then retry the operation. | error | Yes | 503 |
| DALP-14276 | `WALLET_RESOLUTION_INVALID` | domain | The wallet could not be resolved from its stored data. | The wallet's stored data or the resolver input is inconsistent: a factory, identity or participant is missing, or the multisig members, signers or threshold cannot form a valid wallet. | Repair the wallet data or the resolver input, then retry the operation. | error | No | 503 |
| DALP-14277 | `custody.user.PERSONAL_ACCOUNT_LIMIT` | domain | You already have a managed custody account on this network. | A user holds one managed custody account on each network, and the signed-in user already holds one on the network this request resolved to. Nothing was created. | Use the custody account the network already holds, or switch to a network where you have none. | info | No | 409 |

The previous page is [DALP-14100 to DALP-14199](https://docs.settlemint.com/docs/api-reference/errors/platform-api-error-reference/dalp-14100-14199). The next page is [DALP-14300 to DALP-14399](https://docs.settlemint.com/docs/api-reference/errors/platform-api-error-reference/dalp-14300-14399).