# Platform API Error Reference Source: https://docs.settlemint.com/docs/api-reference/errors/platform-api-error-reference Complete reference of all Platform API error codes returned by the DALP API, with HTTP status, retryability, and remediation guidance. {/* ENTRY_COUNT:600 */} {/* SURFACE_COUNT:9 */} # Platform API error reference [#platform-api-error-reference] DALP returns Platform API error identifiers as stable, machine-readable values in API error responses. Use this page when a Platform API client receives a `DALP-####` code and needs to decide whether to fix the request, refresh indexed state, or retry later. Each error in the registry maps to an HTTP status, retry flag, user-facing reason, and recommended recovery step. SDK clients expose the same fields on `DalpSdkError`: `id`, `category`, `status`, `retryable`, `message`, `why`, `fix`, and optional redacted `details`. REST and RPC callers should read these fields from the public error envelope instead of matching on free-text messages. Retry only when the row marks the error as retryable. For retryable dependency or indexing errors, retry with a short backoff and check the affected resource state before resubmitting mutating operations. For non-retryable client, auth, permission, domain, or contract errors, change the request, credentials, permissions, token state, or upstream provider configuration before trying again. If an error tells you to contact support, include the request id from the API response or logs. Do not send secrets, raw signatures, private keys, or unredacted identity documents. Contract revert errors keep their contract-specific data, while Platform API registry metadata explains the API envelope and the safe client response. Compliance-provider errors may require provider-side checks: [Sumsub](https://docs.sumsub.com/), [Elliptic](https://developers.elliptic.co/), [Notabene](https://devx.notabene.id/). ## How to use this reference [#how-to-use-this-reference] 1. Match the `id` in the error envelope to the table row. 2. Check the HTTP status and category to separate request problems from permission, domain, dependency, contract, and operational failures. 3. Use `retryable` as the retry gate. A `yes` means the condition may clear after indexing, dependency recovery, workflow completion, or another transient state change. A `no` means the caller must change something first. 4. Follow the row's fix text. For mutating operations, verify current resource or transaction state before retrying so the client does not submit the same operation twice. ## Errors [#errors] | ID | Category | HTTP status | Retryable | Why | Fix | | ----------- | ----------- | ----------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `DALP-0001` | client | 400 | no | The request is malformed or cannot be understood by the API. | Check the request syntax, parameters, and content type before retrying. | | `DALP-0002` | auth | 401 | no | The request did not include valid authentication credentials. | Authenticate again or send a valid API key/session credential. | | `DALP-0003` | permission | 403 | no | The authenticated actor does not have permission to complete this request. | Use an actor with the required role or ask an administrator to grant access. | | `DALP-0004` | auth | 403 | no | The authenticated user has not completed onboarding required for this operation. | Complete onboarding and retry the request. | | `DALP-0005` | auth | 403 | no | The operation requires wallet-signing protection that is not configured for this user. | Set up PIN or two-factor authentication and retry. | | `DALP-0006` | permission | 403 | no | The actor lacks at least one role required by the token or system contract. | Grant the required role or retry with an authorized actor. | | `DALP-0007` | permission | 403 | no | The encrypted XvP settlement secret could not be decrypted with the caller's current wallet signature. | Retry with the same wallet credentials that were used when the settlement secret was created. | | `DALP-0008` | operational | 500 | no | Platform API could not determine the effective participant executor for this request after checking the session, organization context, and request headers. | Retry with a valid active organization, X-Participant, and X-Executor header combination. If the problem continues, contact support with the request id. | | `DALP-0009` | auth | 500 | no | Platform API could not resolve the authenticated session from the request headers. | Retry with a fresh session or API key. If the problem continues, contact support with the request id. | | `DALP-0010` | dependency | 503 | yes | Platform API could not build the system context from indexed system registry data. | Retry after the indexer catches up. If the problem continues, contact support with the request id. | | `DALP-0011` | dependency | 503 | yes | Platform API could not complete a transaction queue operation outside the known contract-error and Workflow Engine error mappings. | Retry after a short backoff. If the problem continues, contact support with the request id. | | `DALP-0012` | dependency | 503 | yes | The configured chain RPC provider could not read transaction state for this request. | Retry after a short backoff. If the problem continues, contact support with the request id. | | `DALP-0013` | dependency | 503 | yes | Platform API could not preview, sign, or submit the smart-wallet approval workflow after reserving the account-abstraction nonce. | Retry after a short backoff. The nonce reservation is released best-effort and stale reservations expire automatically. | | `DALP-0014` | dependency | 503 | yes | Platform API could not query the Workflow Engine admin plane to determine whether an organization deployment workflow is active. | Retry after a short backoff. If deployment state still cannot be checked, contact support with the request id. | | `DALP-0015` | operational | 503 | yes | The system deployment workflow reached a failed state before producing a usable system address. | Inspect the deployment status and retry after correcting the workflow failure. Include the request id when contacting support. | | `DALP-0016` | operational | 504 | yes | The deployment workflow stayed active but did not publish the system address within the synchronous wait window. | Poll the deployment status or retry with an asynchronous preference instead of waiting for the address in the same request. | | `DALP-0017` | dependency | 503 | yes | Platform API could not resolve a system factory contract address from the request or directory service before starting deployment. | Retry after the system directory has been configured, or pass an explicit system factory contract address. | | `DALP-0018` | operational | 503 | no | The signer rotation transaction was confirmed, but the Platform API could not promote the new signer secret into the secrets provider. | Do not retry blindly. Check the pending signer secret state and rollback status, then recover or rerun the rotation with operator oversight. | | `DALP-0019` | dependency | 503 | yes | An indexer aggregate count could not be converted into a non-negative JavaScript safe integer for the API response. | Retry after the indexer data has been corrected or reindexed. If it continues, contact support with the request id and affected stats endpoint. | | `DALP-0020` | dependency | 503 | yes | The deployment event stream could not read the latest workflow status from the Workflow Engine. | Reconnect to the stream or poll deployment status after a short backoff. If it continues, contact support with the request id. | | `DALP-0021` | operational | 503 | no | The deployment workflow ended with a Workflow Engine terminal error before the stream could read a typed failed workflow tree. | Open the deployment details or retry only after correcting the workflow failure. Include the request id when contacting support. | | `DALP-0022` | client | 404 | no | The requested resource could not be found. | Check the identifier and retry only if the resource should exist. | | `DALP-0023` | client | 409 | no | The request tried to create or register a resource that already exists. | Use the existing resource or choose a unique identifier. | | `DALP-0024` | client | 409 | no | The requested change conflicts with the current resource state. | Refresh the resource state, resolve the conflict, and retry. | | `DALP-0025` | domain | 422 | no | The target token does not expose the interface required for this operation. | Use a compatible token contract or enable the required interface before retrying. | | `DALP-0026` | domain | 403 | no | The DALP system bootstrap has not completed for this environment or organization. | Create or finish deploying the system before calling this operation. | | `DALP-0027` | domain | 501 | no | The requested capability depends on an addon that is not available in this system. | Install or deploy the required addon before retrying the operation. | | `DALP-0028` | domain | 422 | no | The operation targets a token feature that is not attached or enabled. | Enable the required token feature or call an operation supported by this token. | | `DALP-0029` | domain | 403 | no | The authenticated user's email does not match the invitation recipient. | Sign in with the invited email address or ask an admin to send a new invitation. | | `DALP-0030` | domain | 409 | no | The invitation token has already been used successfully. | Continue to the dashboard or ask an admin for a new invitation if access is still missing. | | `DALP-0031` | operational | 504 | yes | The transaction was submitted but confirmation did not arrive before the timeout. | Check transaction status using the transaction hash and retry only if it was not confirmed. | | `DALP-0032` | permission | 403 | no | The operation requires elevated permissions and the authenticated actor does not hold the role required for this route. | Retry with an account that has the role required by this route, or check the route documentation for the required role. | | `DALP-0033` | operational | 500 | no | The route or middleware ran without databaseMiddleware even though it needs database access to validate permissions or load resources. | Contact support with the request id; this indicates a server middleware ordering issue. | | `DALP-0034` | permission | 403 | no | The request requires organization-scoped permissions, but the session does not have an active organization selected. | Select an organization, refresh the session, and retry the request. | | `DALP-0035` | permission | 403 | no | The request uses a read-only API key on a method that can mutate state. | Use a read-write API key or send the request with a safe read method. | | `DALP-0036` | auth | 403 | no | The request used API key authentication on an endpoint that only accepts session authentication. | Call the REST endpoint with the API key, or authenticate with a supported session for RPC. | | `DALP-0037` | operational | 500 | no | A token-scoped route ran before token middleware attached the indexed token context. | Contact support with the request id; this indicates a server middleware ordering issue. | | `DALP-0038` | operational | 500 | no | The route requires token permissions, but token middleware did not attach user permission state. | Contact support with the request id; this indicates a server middleware ordering issue or missing indexed permission data. | | `DALP-0039` | dependency | 404 | yes | The system exists or is being created, but indexed registry children required by this operation are not available yet. | Retry after the indexer catches up. If the system was never deployed, deploy it first. | | `DALP-0040` | client | 404 | no | The operation requires an indexed system deployment, but none is available for the active organization. | Deploy a system for the organization, wait for indexing, and retry. | | `DALP-0041` | dependency | 500 | yes | The system was indexed without the access-control state required to evaluate the caller's roles. | Retry after indexing catches up. If the problem continues, contact support with the request id. | | `DALP-0042` | dependency | 500 | yes | The route could not load indexed trusted-issuer context for the active system. | Retry after indexing catches up. If the problem continues, contact support with the request id. | | `DALP-0043` | permission | 403 | no | The user's issuer identity is not trusted for the claim topic being mutated. | Use a trusted issuer for the topic, or ask a system manager to trust this issuer for the topic. | | `DALP-0044` | permission | 403 | no | The operation requires a registered issuer identity for the authenticated user. | Register an issuer identity for the user, then retry. | | `DALP-0045` | dependency | 503 | yes | Platform API could not contact the Ledger Index Indexing Pipeline service that starts blockchain reindex jobs. | Retry after a short backoff. If the problem continues, contact support with the request id. | | `DALP-0046` | client | 400 | no | The requested blockchain reindex range, target, or mode was rejected by the Ledger Index reindex admin. | Adjust the reindex request to a supported chain, range, and mode before retrying. | | `DALP-0047` | dependency | 503 | yes | The Ledger Index reindex admin accepted the request path but reported that reindexing cannot be started now. | Retry after a short backoff. If the problem continues, contact support with the request id. | | `DALP-0048` | client | 404 | no | No API monitoring log entry exists for the requested id in the active organization. | Verify the log entry id and organization, then retry. | | `DALP-0049` | client | 400 | no | The request type filter does not match a request type known to API monitoring. | Use one of the documented request type values, or omit the filter. | | `DALP-0051` | client | 404 | no | No invitation matching the requested id exists for the caller. | Check the invitation link or ask the organization to issue a new invitation. | | `DALP-0052` | client | 403 | no | The invitation exists but its expiry time has passed. | Ask the organization to send a fresh invitation. | | `DALP-0053` | client | 403 | no | The invitation was explicitly revoked or is no longer in an accepted state for this flow. | Ask the organization to send a fresh invitation. | | `DALP-0054` | client | 404 | no | The requested deployment id is malformed, stale, or does not belong to a deployment the caller may observe. | Refresh deployment state and subscribe using the current deployment id. | | `DALP-0055` | permission | 403 | no | Retrying deployment mutates organization settings and on-chain system state, so member-level access is not sufficient. | Retry with an organization owner or platform administrator account. | | `DALP-0056` | dependency | 503 | yes | Platform API could not safely inspect or purge the previous Workflow Engine workflow before submitting a retry. | Retry after a short backoff. If the problem continues, contact support with the request id. | | `DALP-0057` | permission | 403 | no | The deployment is creating a new organization while the environment restricts organization creation to platform admins. | Ask a platform admin to create the organization or disable the restriction for this environment. | | `DALP-0058` | dependency | 503 | yes | The system directory did not return the factory address required to start deployment. | Retry after directory configuration has propagated. If the problem continues, contact support with the request id. | | `DALP-0059` | client | 404 | no | The settlement exists but the encrypted secret payload is missing from XvP secret storage. | Verify the settlement address and ensure the secret was created before decrypting. | | `DALP-0060` | client | 400 | no | The stored secret payload was encrypted with a method this Platform API version does not support. | Recreate the settlement secret with the supported encryption method. | | `DALP-0061` | client | 400 | no | A cross-chain XvP settlement was created with a hashlock that is not valid hex. | Send a 0x-prefixed hashlock or provide the secret so the API can derive it. | | `DALP-0062` | client | 400 | no | The settlement includes an external flow, so a secret or precomputed hashlock is required to coordinate settlement. | Provide a settlement secret or a valid hashlock in the request. | | `DALP-0063` | client | 404 | yes | The requested factory address is not indexed as an XvP settlement addon for the authenticated system. | Use an installed XvP factory address or retry after addon indexing catches up. | | `DALP-0064` | client | 400 | no | The selected XvP factory version requires an ISO 3166-1 numeric country code. | Include a valid country code in the XvP creation request. | | `DALP-0065` | client | 404 | yes | The authenticated system does not have an indexed XvP settlement addon. | Install the XvP settlement addon or retry after indexing catches up. | | `DALP-0066` | client | 404 | no | The request references a system addon address that is not part of the caller's active system. | Use an addon address from the authenticated system. | | `DALP-0067` | client | 400 | no | The XvP list request needs a participant wallet filter and the authenticated user does not have a wallet to use as the default. | Provide a participant wallet filter or complete wallet onboarding. | | `DALP-0068` | client | 404 | yes | The requested settlement address is not indexed for the authenticated system. | Verify the settlement address or retry after indexing catches up. | | `DALP-0069` | permission | 403 | no | The caller is not the local sender recorded for the XvP settlement flow. | Approve from the wallet that is the local sender for this settlement. | | `DALP-0070` | client | 404 | no | The caller has not approved the requested XvP settlement or the approval is not indexed. | Approve the settlement first or retry after indexing catches up. | | `DALP-0071` | client | 400 | no | The XvP signature payload is not a 0x-prefixed hexadecimal value. | Sign the settlement message again and submit the hex-encoded signature. | | `DALP-0072` | permission | 403 | no | The authenticated user has no wallet id available for signing the XvP settlement message. | Complete wallet onboarding, refresh the session, and retry. | | `DALP-0073` | dependency | 503 | yes | The wallet signing service failed while signing the XvP settlement message. | Retry after a short backoff. If signing continues to fail, contact support with the request id. | | `DALP-0074` | client | 404 | yes | The requested fixed-yield schedule is not indexed for the authenticated system or addon. | Verify the schedule address or retry after indexing catches up. | | `DALP-0075` | dependency | 503 | yes | The fixed-yield schedule references a denomination asset whose metadata is not available in the indexer. | Retry after indexing catches up. | | `DALP-0076` | dependency | 503 | yes | The fixed-yield operation needs the denomination asset row, but the indexer has not exposed it yet. | Retry after indexing catches up. | | `DALP-0077` | permission | 403 | no | The requested fixed-yield schedule is associated with a different system than the caller's active system. | Use a schedule address from the authenticated system. | | `DALP-0078` | client | 404 | yes | The authenticated system does not have the fixed-yield addon indexed. | Install the addon or retry after indexing catches up. | | `DALP-0079` | dependency | 503 | yes | The fixed-yield deployment transaction completed but the created schedule is not visible in the indexer yet. | Retry after indexing catches up. | | `DALP-0080` | client | 422 | no | The request body or parameters did not match the API contract. | Check the request fields against the API documentation and retry with valid values. | | `DALP-0081` | contract | 422 | no | The smart contract rejected the operation with a known DALP error. | Use the DALP code and suggested response step to correct the request or token state. | | `DALP-0082` | dependency | 503 | yes | A required backend service is temporarily unavailable. | Retry after a short backoff. If the problem continues, contact support with the request id. | | `DALP-0083` | dependency | 503 | yes | Platform API is reading from an indexer schema that is still rolling out or reindexing. | Retry after the indexer rollout completes. If the problem continues, contact support with the request id. | | `DALP-0084` | unknown | 500 | no | Platform API could not complete the request because an unexpected server error occurred. | Retry later or contact support with the request id if the problem continues. | | `DALP-0085` | client | 400 | no | The JSON-RPC request is missing required fields or uses an unsupported shape. | Send a valid JSON-RPC 2.0 request with the required method, id, and params fields. | | `DALP-0086` | operational | 500 | yes | Platform API could not continue the event stream safely. | Reconnect to the stream. If failures continue, contact support with the request id. | | `DALP-0087` | permission | 404 | no | The resource does not exist or is not available to the current actor. | Check that the identifier is correct and that the actor has access to this resource. | | `DALP-0088` | client | 404 | no | The platform looked up the asset class definition by the supplied ID and found no record visible to your organization. A definition is visible if your organization owns it or it is a platform-wide system class. | Confirm the ID matches an existing definition owned by your organization or a system class. Re-fetch the list of asset class definitions to verify the ID before retrying. | | `DALP-0089` | client | 404 | no | The platform searched for the asset class definition scoped to your organization and found no matching record. System class definitions are outside the delete scope and return this error when targeted. | Confirm the ID corresponds to a custom definition owned by your organization. Re-fetch your organization's asset class definitions to verify the ID before retrying. | | `DALP-0090` | client | 404 | no | The platform verified the definition existed at the start of the update, but by the time it applied the change or re-read the result, the record was no longer present. A parallel delete request is the most likely cause. | Re-fetch the asset class definition to confirm it still exists before retrying the update. If the definition was deleted, recreate it or use a different definition ID. | | `DALP-0091` | client | 404 | no | The platform searched for the asset type template by the supplied ID and found no record owned by your organization or available as a system template. | Confirm the ID matches an existing template owned by your organization or a published system template. Re-fetch the list of asset type templates to verify the ID before retrying. | | `DALP-0092` | dependency | 503 | yes | The platform could not resolve an active organization from the authenticated session. This is required for user administration operations. | Include a valid `X-Organization` header that matches an organization the authenticated user belongs to, then retry. | | `DALP-0093` | dependency | 503 | yes | The identity recovery execute route requires an active organization context from the session. The `X-Organization` header was absent or did not resolve to a known organization. | Set the `X-Organization` header to a valid organization identifier and retry the request. | | `DALP-0094` | dependency | 503 | yes | The identity recovery preview route requires an active organization context from the session. The `X-Organization` header was absent or did not resolve to a known organization. | Set the `X-Organization` header to a valid organization identifier and retry the request. | | `DALP-0095` | client | 404 | no | No compliance template matching the requested ID exists within the calling organization's scope. The platform queries both organization-owned and shared system templates; a mismatch on either the ID or the owning organization returns this error. | Confirm the template ID belongs to your organization or is a system template, then retry the request. | | `DALP-0096` | client | 404 | no | No address-book contact with the given identifier exists for the authenticated user. The contact may have been deleted or the identifier belongs to a different user. | Verify the contact identifier against the contacts list for this user, then retry with a valid `id`. | | `DALP-0097` | operational | 500 | no | The platform wrote the new contact record but the follow-up read returned no row. This is a transient database consistency gap rather than a validation problem. | Retry the request. If the error persists, contact support with the request ID. | | `DALP-0098` | operational | 500 | no | The platform attempted to insert the contact row but the database returned no record. This can occur when the insert is silently dropped by a constraint or database-level rule before a row is committed. | Retry the request. If the error persists, contact support with the request ID. | | `DALP-0099` | client | 400 | no | A batch operation received an empty array for `{fieldName}`. The platform requires at least one element to proceed. | Provide at least one element in `{fieldName}` and retry the request. | | `DALP-0100` | client | 400 | no | A batch operation received arrays of different lengths. All arrays supplied to the same batch call must have the same number of elements. | Ensure every array in the request has the same element count, then retry. | | `DALP-0101` | client | 400 | no | The array provided for `{fieldName}` contains more elements than this batch operation allows. | Split the request into smaller batches that each stay within the documented element limit, then retry. | | `DALP-0102` | operational | 500 | no | The platform found more than one non-revoked, non-expired claim for topic `{topicId}` on identity `{identityAddress}`. Only one active claim per topic per identity is expected; this state indicates a data consistency issue in the claim registry. | Contact support with the request id so the duplicate claims can be investigated and resolved. | | `DALP-0103` | client | 404 | no | The platform found no non-revoked, non-expired claim for topic `{topicId}` on identity `{identityAddress}` in the claim registry. | Verify that the claim was issued and has not expired or been revoked, then retry. | | `DALP-0104` | client | 404 | no | The platform could not find an enabled topic scheme named `{topicId}` in the registry at `{registryAddress}`. The topic scheme may not have been registered or may have been disabled. | Verify the topic name is correctly spelled and enabled in the system's topic scheme registry, then retry. | | `DALP-0105` | client | 404 | no | The signing wallet for the participant has no key identifier (`walletId`), which the platform requires to submit a claim issuance transaction. This typically means the user's wallet was not fully provisioned. | Complete wallet provisioning for this user, ensure the session includes `walletId`, and retry. | | `DALP-0106` | client | 404 | no | The signing wallet for the participant has no key identifier (`walletId`), which the platform requires to submit a claim revocation transaction. This typically means the user's wallet was not fully provisioned. | Complete wallet provisioning for this user, ensure the session includes `walletId`, and retry. | | `DALP-0107` | client | 400 | no | The value supplied for `baseCurrency` is not a recognized fiat currency code. The currency conversion helper only accepts standard fiat currency codes. | Supply a supported fiat currency code (for example `USD`, `EUR`, `GBP`) as `baseCurrency` and retry. | | `DALP-0108` | operational | 500 | no | The platform's query builder returned no SQL condition when at least one was required. This indicates a route dispatch or configuration error, not a problem with the request data. | Contact support with the request id and route name so the underlying configuration issue can be diagnosed. | | `DALP-0109` | client | 400 | no | The platform resolved feature `{featureName}` from the token's indexed configuration, but the stored address `{address}` is not a valid Ethereum address. This indicates a data integrity issue in the feature registry. | Contact support with the request id. The feature address stored in the indexer needs to be investigated. | | `DALP-0110` | operational | 500 | no | The operation requires the `{featureName}` feature, but no attached feature of that type was found in the token's indexed configuration. | Attach the `{featureName}` feature to the token via the token configuration before calling this endpoint. | | `DALP-0111` | dependency | 503 | yes | The transaction queue helper started without a database connection attached to the request context. This happens when the route's middleware chain did not attach a database session before calling the queue. | Contact support with the request id. This indicates a server configuration issue, not a problem with the request itself. | | `DALP-0112` | client | 400 | no | The system address from the request or the active system context did not pass Ethereum address validation. The value is either malformed or not a checksummed EVM address. | Provide a valid 0x-prefixed Ethereum address for the system address field and retry. | | `DALP-0113` | dependency | 503 | yes | The transaction queue helper started without a workflow engine client attached to the request context. The platform requires this client to submit and track on-chain transactions. | Retry after a short backoff. If the problem continues, contact support with the request id. | | `DALP-0114` | client | 400 | no | The transaction queue completed synchronously but the route did not supply a `readResult` callback, so no response data could be constructed from the confirmed transaction. | Contact support with the request id. This is a server-side integration issue, not a problem with the request itself. | | `DALP-0115` | domain | 409 | no | A v1 route handler received an async-accepted result from the transaction queue. V1 routes always execute in synchronous mode, so this result is a dispatch logic error on the platform side. | Contact support with the request id and the route name. This indicates a server-side bug and cannot be resolved by changing the request. | | `DALP-0116` | client | 404 | no | No active FX feed covers the requested currency pair on the current chain, or the feed exists but has not yet recorded an observed rate. | Check the supported currencies list to confirm the pair is available. If the pair was recently added, retry after the feed publishes its first observation. | | `DALP-0117` | client | 404 | no | The requested base currency is not recognized as a supported fiat currency code for exchange rate operations. | Use the supported currencies endpoint to retrieve the list of accepted base currency codes, then retry with a valid value. | | `DALP-0118` | operational | 500 | no | The platform could not retrieve exchange rate data from the configured rate source. The fetch attempt returned an error. | Retry after a short backoff. If the problem continues, contact support with the request id. | | `DALP-0119` | client | 404 | no | The platform looked for a manually configured exchange rate for the requested currency pair but found no entry. | Configure a manual exchange rate for the `{baseCurrency}`/`{quoteCurrency}` pair before retrying this operation. | | `DALP-0120` | client | 404 | no | The requested quote currency is not recognized as a supported fiat currency code for exchange rate operations. | Use the supported currencies endpoint to retrieve the list of accepted quote currency codes, then retry with a valid value. | | `DALP-0121` | client | 404 | no | The platform could not locate an `ExternalTokenRegistry` contract linked to this system. The registry must be deployed and registered before external tokens can be registered. | Verify that the system has an `ExternalTokenRegistry` deployed and that its address is registered in the system configuration. | | `DALP-0122` | client | 404 | no | The platform could not locate an `ExternalTokenRegistry` contract linked to this system. The contract must be deployed and its address registered before external tokens can be registered. | Deploy an `ExternalTokenRegistry` contract for the system and register its address in the system configuration, then retry the registration. | | `DALP-0123` | domain | 409 | no | The authenticated participant does not have an on-chain identity contract registered in this system. Feed submissions require an identity so the platform can verify the participant as a trusted issuer. | Deploy an identity contract for the participant through the identity management flow, then retry the feed submission. | | `DALP-0124` | client | 404 | no | The adapter creation transaction completed, but the platform could not find a matching `AdapterCreated` event in the transaction receipt logs for the requested subject and topic. The log may belong to a different factory or was not emitted. | Check the transaction on-chain to confirm the adapter was created for the correct subject and topic. If the adapter exists, retrieve its address directly from the transaction receipt. | | `DALP-0125` | client | 404 | no | The platform could not find a feed at the given address in the system index. The feed may not have been registered, or the indexer has not yet processed its registration event. | Confirm the feed address is correct and the feed has been registered in the system. If the feed was recently registered, wait for the indexer to catch up and retry. | | `DALP-0126` | client | 400 | no | The platform attempted to call the `AggregatorV3` interface on the given address and the call failed. The contract at that address does not implement the expected interface or is not deployed on the current network. | Verify the feed address is correct and that the contract is deployed on the target network. Confirm the contract exposes the `AggregatorV3` interface. | | `DALP-0127` | client | 404 | no | The platform could not find a `FeedsDirectory` address for this system in the index. This means the system has not completed its V3 bootstrap, or the indexer has not yet processed the bootstrap event. | Complete the V3 bootstrap for the system and wait for the indexer to process the event before retrying. | | `DALP-0128` | client | 404 | no | The feed creation transaction completed, but the platform could not find a matching `FeedCreated` event in the transaction receipt logs for the requested subject and topic. The log may belong to a different factory or was not emitted. | Check the transaction on-chain to confirm the feed was created for the correct subject and topic. If the feed exists, retrieve its address directly from the transaction receipt. | | `DALP-0129` | dependency | 503 | yes | The platform could not find an active feed for the given subject and topic identifier in the system index. The feed may not have been registered, or the indexer has not yet processed its registration. | Confirm the feed has been registered for the subject and topic, then retry after the indexer catches up. Contact support with the request ID if the problem persists. | | `DALP-0130` | client | 400 | no | The `topicId` value provided is not a numeric string. The platform requires `topicId` to contain only digit characters so it can be parsed as a number. | Supply `topicId` as a string of digits only (for example `"42"`), or provide `topicName` instead to let the platform derive the topic identifier. | | `DALP-0131` | client | 404 | no | The feed contract does not have data for the requested round. The round may not exist, or the feed is configured to retain only the latest value and does not store historical rounds. | Verify the round ID is correct. If the feed is in `LATEST_ONLY` mode, historical round data is not available. | | `DALP-0132` | client | 400 | no | The transaction queue returned a hash value that is not a valid `0x`-prefixed hexadecimal string. This indicates an internal state issue with the transaction result. | Retry the operation. If the error persists, contact support with the request ID and the transaction hash value shown in the message. | | `DALP-0133` | dependency | 503 | yes | The workflow engine returned a transaction hash that is not a valid `0x`-prefixed hexadecimal string. This indicates an internal state issue in the feed submission workflow. | Retry the feed submission. If the error persists, contact support with the request ID and the transaction hash value shown in the message. | | `DALP-0134` | client | 404 | no | The platform located an identity contract for the user but the identity factory address is missing from the index record. This points to an incomplete index entry for the identity. | Contact support with the request ID. This condition requires platform-side investigation to repair the index record. | | `DALP-0135` | operational | 500 | no | The target user's wallet is a multisig or shared wallet. The identity recovery flow currently supports only single-owner personal smart wallets. | Recovery for multisig and shared wallets is not yet available. Use a single-owner personal smart wallet or EOA for recovery at this time. | | `DALP-0136` | client | 404 | no | The platform could not find a running or recently completed recovery workflow for the specified user. Either no recovery was initiated, or the workflow service could not be reached. | Confirm a recovery workflow was started for the user. If the recovery was just initiated, wait a moment and retry. Contact support with the request ID if the problem continues. | | `DALP-0137` | client | 400 | no | No wallet address was included in the request, and the platform could not resolve a default executor wallet for this user in the active organization. The user may not yet have a wallet provisioned. | Include a `wallet` field in the request body with a valid wallet address that belongs to the target user. | | `DALP-0138` | client | 400 | no | No wallet address was included in the request, and the platform found no personal signing or smart wallet for this user. The user's personal wallet may not have been created yet. | Include a `wallet` field in the request body with a valid wallet address that belongs to the target user. | | `DALP-0139` | operational | 500 | no | The platform queried the indexer for an identity contract on the user's wallet addresses and found none. Identity recovery requires an on-chain identity to exist before it can be recovered. | Deploy an identity contract for this user through the identity management flow before attempting recovery. | | `DALP-0140` | client | 404 | no | No user matching the provided ID was found within the caller's organization. The user may not exist or may not be a member of this organization. | Confirm the user ID is correct and that the user is a member of the active organization before retrying. | | `DALP-0141` | permission | 403 | no | The wallet address provided in the request is not registered as belonging to the target user's participant record. Only wallets owned by the target user are permitted for recovery. | Use a wallet address that is registered to the target user, or retrieve the user's wallets from the participants API first. | | `DALP-0142` | dependency | 503 | yes | The route handler reached a KYC action-requests query that is unavailable because the KYC database schema was not registered for this route context. This is a server configuration issue. | Contact support with the request ID. This indicates a route or middleware composition problem that requires a platform fix. | | `DALP-0143` | dependency | 503 | yes | The route handler reached a KYC documents query that is unavailable because the KYC database schema was not registered for this route context. This is a server configuration issue. | Contact support with the request ID. This indicates a route or middleware composition problem that requires a platform fix. | | `DALP-0144` | dependency | 503 | yes | The route handler reached a KYC profiles query that is unavailable because the KYC database schema was not registered for this route context. This is a server configuration issue. | Contact support with the request ID. This indicates a route or middleware composition problem that requires a platform fix. | | `DALP-0145` | dependency | 503 | yes | The route handler reached a KYC versions query that is unavailable because the KYC database schema was not registered for this route context. This is a server configuration issue. | Contact support with the request ID. This indicates a route or middleware composition problem that requires a platform fix. | | `DALP-0146` | dependency | 503 | yes | The platform could not reach the object storage service. The storage backend may be unreachable, or the object storage provider is not configured for this organization. | Retry the request. If the problem persists, contact support with the request ID. | | `DALP-0147` | permission | 403 | no | The permission check on the active organization failed. The organization has not been granted the off-chain permission required by this route. | Ask an administrator to grant the required permission to this organization, then retry. | | `DALP-0148` | permission | 403 | no | The permission check on the authenticated user failed. The user has not been granted the off-chain permission required by this route. | Ask an administrator to grant the required user-level permission, then retry. | | `DALP-0149` | permission | 403 | no | A wallet header was present in the request but the caller does not have permission to use it in this context. | Remove the wallet header from the request, or use a wallet address that is authorized for this operation. | | `DALP-0150` | client | 400 | no | A wallet header was present in the request but the value did not match the expected format or accepted set of values. | Check the wallet header value and ensure it is a valid, correctly formatted address or accepted token. | | `DALP-0151` | dependency | 503 | yes | A call to the workflow execution service returned an error that does not map to a more specific error code. The service may be temporarily unavailable or returned an unexpected response. | Retry the request. If the problem persists, contact support with the request ID. | | `DALP-0152` | domain | 409 | no | Published templates lock the deployable asset path. Changing baseAssetType would change which instrument-specific fields apply to assets already created from this template. | Create a new template with the desired base asset type instead of changing a published one. | | `DALP-0153` | domain | 409 | no | The template has already been published and its `typeId` is locked. Published templates cannot change `typeId` because doing so would alter the instrument type for assets already deployed from this template. | Create a new template with the desired `typeId` instead of modifying a published one. | | `DALP-0154` | domain | 409 | no | Setting `assetClassId` to null asks the platform to revert to the system-derived asset class for the template's base type, but the `typeId` value on this template does not map to any known factory type, so no system class can be resolved. | Supply a valid `assetClassId` explicitly instead of clearing it, or update the template's `typeId` to a recognized deployable asset type before clearing the class. | | `DALP-0155` | domain | 409 | no | The requested asset class is a platform-provided system class. System classes are shared baselines and cannot be removed. | Delete only custom asset classes that your organization created. System classes remain available to all organizations and cannot be removed. | | `DALP-0156` | domain | 409 | no | The requested asset class is a platform-provided system class. Metadata fields such as name, slug, and description are read-only on system classes. | Create a custom asset class with the desired name and configuration. Visibility (`isHidden`) can still be toggled on any system class your organization can see. | | `DALP-0157` | operational | 500 | no | The database insert for the new asset class definition completed without returning a row. This typically indicates a transient database connectivity problem on the write path. | Retry the request. If the error persists, contact support with the request ID and the endpoint path. | | `DALP-0158` | operational | 500 | no | The database insert for the new asset type template returned no row. Duplicate-name and slug-collision paths are handled separately, so this path fires when the write fails due to a connectivity or transient storage problem. | Retry the request. If the error persists, contact support with the request ID and the endpoint path. | | `DALP-0159` | client | 400 | no | The `assetClassId` provided does not match any asset class visible to the requesting organization. The class either belongs to a different organization or does not exist. | Supply an `assetClassId` that belongs to your organization or is a platform system class. Retrieve the list of available classes from the asset class definitions endpoint. | | `DALP-0160` | domain | 409 | no | The requested asset type template is a platform-provided system template. System templates are shared baselines and cannot be removed. | Delete only custom asset type templates that your organization created. To hide a system template from your organization's view, set `isHidden` to `true` on the template. | | `DALP-0161` | domain | 409 | no | The requested asset type template is a platform-provided system template. Fields such as name, description, typeId, and feature configuration are read-only on system templates. | Update only custom asset type templates that your organization created. The `isHidden` display preference can still be toggled on any system template your organization can see. | | `DALP-0162` | domain | 409 | no | The requested asset type template is a platform-provided system template. System templates are already active and their publication state cannot be changed. | Publish only custom draft asset type templates that your organization created. | | `DALP-0163` | operational | 500 | no | The `typeId` being set is not a deployable asset type, so the platform cannot derive `baseAssetType` automatically. This check runs when `typeId` is changed on a template and no explicit `baseAssetType` is supplied. | Supply a `baseAssetType` value alongside the `typeId` in the request body, or use a `typeId` that corresponds to a directly deployable asset type. | | `DALP-0164` | client | 400 | no | The `typeId` value supplied when creating the template does not match any type registered in the platform's asset type registry. | Provide a `typeId` from the list of recognized asset types. Check the asset type reference documentation for the set of supported values. | | `DALP-0165` | operational | 500 | no | The database insert for the new compliance template returned no row. Name-collision handling runs before this path, so this indicates a transient connectivity or storage failure on the write. | Retry the request. If the error persists, contact support with the request ID and the endpoint path. | | `DALP-0166` | operational | 500 | no | The database update for the compliance template returned no row. All ownership and system-template guards passed before the write, so this indicates a transient storage failure. | Retry the request. If the error persists, contact support with the request ID and the endpoint path. | | `DALP-0167` | domain | 409 | no | The requested compliance template is a platform-provided system template. System templates are shared baselines and cannot be removed. | Delete only custom compliance templates that your organization created. | | `DALP-0168` | domain | 409 | no | The requested compliance template is a platform-provided system template. All fields on system compliance templates are read-only. | Modify only custom compliance templates that your organization created. To build on a system template's configuration, create a new custom compliance template. | | `DALP-0169` | domain | 409 | no | The requested compliance template is a platform-provided system template. System templates are already active and their publication state cannot be changed. | Publish only custom draft compliance templates that your organization created. | | `DALP-0170` | operational | 500 | no | The platform persisted all prerequisite steps for this setting key but the final database write returned no row. For `TARGET_CURRENCIES` this occurs after feed dispatch; for `AA_ENABLED` after on-chain sync; for other keys on the direct write path. | Retry the request. If the error persists, contact support with the request ID, the setting key, and the endpoint path. | | `DALP-0171` | client | 404 | no | The `orgId` supplied in the global theme request does not match any organization in the platform. The organization may not exist or may have been deleted. | Verify the `orgId` value and confirm the organization exists before setting it as the global theme source. | | `DALP-0172` | client | 404 | no | No setting record with the requested key exists for the authenticated organization. The key may be misspelled or the setting may not have been created. | Verify the setting key and confirm it exists for your organization before attempting to delete it. | | `DALP-0173` | client | 400 | no | The decoded logo file data exceeds the maximum permitted upload size. The platform enforces a per-upload file size ceiling on theme logo uploads. | Reduce the file size to within the stated limit and resubmit the request. | | `DALP-0174` | dependency | 503 | yes | The theme logo upload reached the platform's storage layer, but no object storage provider was available for this organization's scope. The storage integration may not be configured. | Contact support with the request id. This indicates object storage has not been provisioned for this deployment. | | `DALP-0175` | client | 400 | no | One or more fields in the submitted theme configuration exceed the platform's size or structural constraints. This is checked before any data is stored. | Review the `violations` detail returned with this response and reduce the offending field values to within the stated limits, then resubmit. | | `DALP-0176` | operational | 500 | no | The wallet has no installed MultisigWeightedValidator module, so threshold changes cannot be applied. | Install a MultisigWeightedValidator on the wallet, then retry the threshold change. | | `DALP-0177` | permission | 403 | no | The wallet has no installed MultisigWeightedValidator module, so signer management is unavailable. | Install a MultisigWeightedValidator on the wallet, then retry the signer operation. | | `DALP-0178` | operational | 500 | no | The wallet has no installed MultisigWeightedValidator module, so approval creation is unavailable. | Install a MultisigWeightedValidator on the wallet, then retry approval creation. | | `DALP-0179` | permission | 403 | no | The wallet has no installed MultisigWeightedValidator module, so signer management is unavailable. | Install a MultisigWeightedValidator on the wallet, then retry the signer operation. | | `DALP-0180` | operational | 500 | no | The wallet has no installed MultisigWeightedValidator module, so approval signing cannot proceed. | Install a MultisigWeightedValidator on the wallet, then retry signing the approval. | | `DALP-0181` | client | 404 | no | Platform API could not find a smart-wallet approval matching the user operation hash in the active organization scope. | Verify the userOpHash from the preview or approval creation response, then retry. | | `DALP-0182` | permission | 403 | no | The approval record is scoped to a different wallet than the one in the request path. | Use the wallet address that owns the approval, or create a new approval for this wallet. | | `DALP-0183` | client | 400 | no | The smart-wallet approval request included a user operation hash that is not valid hex, so Platform API cannot safely look up or sign the approval. | Send the exact 0x-prefixed userOpHash returned by the smart-wallet preview or approval creation response. | | `DALP-0184` | permission | 403 | no | The approval record is scoped to a different wallet than the signer session expects. | Sign the approval from a wallet that owns it, or submit signatures only for approvals on that wallet. | | `DALP-0185` | operational | 500 | no | The approval workflow finished without the fields needed to assemble the API response. | Retry the request. If it continues, contact support with the request id and approval id. | | `DALP-0186` | permission | 403 | no | The request wallet is not registered as a signer on the target multisig wallet. | Add the authenticated wallet as a signer, or switch to a wallet that is already on the signers list. | | `DALP-0187` | operational | 500 | no | The smart-wallet preview request included callData that is not valid hex. | Send callData as a 0x-prefixed hex string from the contract call you intend to execute. | | `DALP-0188` | client | 400 | no | The smart-wallet creation request included initData that is not valid hex. | Send initData as a 0x-prefixed hex string, or omit it when the wallet does not need initializer data. | | `DALP-0189` | client | 400 | no | The organization has no provisioned bundler wallet, so smart-wallet operations that depend on account abstraction cannot run. | Complete system deployment so the bundler wallet is provisioned, then retry. | | `DALP-0190` | client | 400 | no | The user session has no bundler wallet configured for smart-wallet signing. | Configure a bundler wallet for the session, then retry the smart-wallet operation. | | `DALP-0191` | permission | 403 | no | The user session has no signer wallet configured for smart-wallet operations. | Configure a signer wallet for the session, then retry. | | `DALP-0192` | permission | 403 | no | The add-signer endpoint requires every new signer to carry weight 1. A weight other than 1 was supplied, and per-signer weight configuration is not yet available on this endpoint. | Submit the request with `weight` set to 1. To assign a different weight, use the dedicated weight-management endpoint after adding the signer. | | `DALP-0193` | permission | 403 | no | The authenticated user's EOAs are not registered as signers on the target multisig wallet. | Re-claim the wallet from a current signer EOA, or ask a wallet owner to add your signer. | | `DALP-0194` | permission | 403 | no | The authenticated EOA is not an owner or registered signer for this smart wallet. | Sign in with an EOA that controls this wallet, or claim the wallet from that EOA first. | | `DALP-0195` | permission | 403 | no | The authenticated wallet is not registered as a signer on the selected multisig validator. | Select a wallet that is a registered signer, or ask a wallet owner to add your signer before retrying. | | `DALP-0196` | permission | 403 | no | The authenticated wallet is not registered as a signer on the selected multisig validator, so it cannot initiate an approval request. | Switch to a registered signer wallet, or ask a wallet owner to add your signer before creating the approval. | | `DALP-0197` | permission | 403 | no | The authenticated wallet is not registered as a signer for the selected smart wallet. | Use a registered signer wallet, or ask a wallet owner to add your signer before retrying. | | `DALP-0198` | permission | 403 | no | The requester is a co-signer, not the wallet owner, and this operation requires owner execution or an approval workflow. | Switch to the owner wallet, or create and collect multisig approvals before executing the operation. | | `DALP-0199` | domain | 409 | no | Account Abstraction is disabled for this organization, so smart wallets cannot be set as the default executor. | Enable Account Abstraction for the organization, or create the smart wallet without setting it as default. | | `DALP-0200` | domain | 409 | no | Account Abstraction is disabled for this organization, so an existing smart wallet cannot be promoted to default. | Enable Account Abstraction for the organization, or update only the smart wallet metadata. | | `DALP-0201` | dependency | 503 | yes | The platform could not resolve a primary RPC URL for this chain from the loaded network configuration. Without an RPC endpoint, the approval workflow cannot be built or submitted. | Verify that the network configuration for this chain includes a valid primary RPC URL, then retry. | | `DALP-0202` | dependency | 503 | yes | The platform could not resolve a primary RPC URL for this chain from the loaded network configuration. Without an RPC endpoint, the live wallet balance cannot be retrieved. | Verify that the network configuration for this chain includes a valid primary RPC URL, then retry the gas-status request. | | `DALP-0203` | operational | 500 | no | The optional systemAddress query parameter does not match the wallet's indexed system address. | Omit systemAddress to use the wallet's own system, or pass the wallet's indexed system address. | | `DALP-0204` | domain | 409 | no | The platform rebuilt a UserOperation preview from the submitted `callData` and the current wallet state, and the computed hash did not match the `userOpHash` supplied in the request. The wallet nonce or state may have changed since the preview was created. | Fetch a fresh preview for the same `callData`, use the `userOpHash` returned by that preview, then submit the approval request again. | | `DALP-0205` | dependency | 503 | yes | The smart wallet creation workflow completed successfully, but the resulting wallet address was not returned in the workflow output. This is a transient result-assembly failure. | Retry the request. If the wallet was created on-chain you can also look it up by the transaction hash. Contact support with the request id if retries do not succeed. | | `DALP-0206` | operational | 500 | no | The metadata write completed, but a follow-up read did not return the updated wallet row. | Refresh the wallet list after a short backoff. If the metadata is still missing, contact support with the request id. | | `DALP-0207` | client | 400 | no | The wallet exists but its multisig threshold is unset, so approval creation is blocked. | Set a multisig threshold on the wallet, then retry approval creation. | | `DALP-0208` | client | 404 | no | The platform could not find a smart wallet at the supplied address within the current organization scope. The wallet may not have been indexed yet, or the address may be from a different organization. | Confirm the wallet address is correct and belongs to this organization. If the wallet was recently created, wait for indexing to complete, then retry. | | `DALP-0209` | client | 404 | no | The platform could not find the smart wallet at the supplied address in the current organization scope. The wallet must be indexed and have a system scope assigned before approvals can be created. | Confirm the wallet address is correct and that the wallet has been indexed and assigned to a system. Wait for indexing to complete if the wallet was recently created, then retry. | | `DALP-0210` | client | 404 | no | The platform could not find a smart wallet at the supplied address in the current organization or system scope. The gas-status endpoint requires the wallet to be present in the indexer before it can check paymaster and balance data. | Confirm the wallet address is correct. If the wallet was recently created, wait for indexing to complete, then retry the gas-status request. | | `DALP-0211` | client | 404 | no | The platform could not find a smart wallet at the supplied address in the current organization scope. The wallet read endpoint requires the wallet to be present in the indexer. | Confirm the wallet address is correct and belongs to this organization. If the wallet was recently created, wait for indexing to complete, then retry. | | `DALP-0212` | client | 404 | yes | The platform found the wallet on-chain but the indexer has not yet recorded it for this organization. Metadata updates require the indexed wallet record to be present. | Wait a short time for the indexer to process the wallet, then retry the update. | | `DALP-0213` | client | 404 | yes | The wallet transaction completed, but the indexer has not yet reflected the AccountCreated event. | Retry after a short backoff while the indexer catches up. | | `DALP-0214` | permission | 403 | no | The request supplied an empty address list or an empty role list after deduplication. The platform requires at least one address and one role to encode a grant-role or revoke-role call. | Include at least one wallet address and one role name in the request body, then resubmit. | | `DALP-0215` | permission | 403 | no | The platform resolved the system context but found no access manager contract address attached to it. The grant-role call cannot be encoded without a target contract. | Verify that the system has a deployed access manager. If the system was recently bootstrapped, confirm the indexer has caught up before retrying. | | `DALP-0216` | permission | 403 | no | The platform resolved the system context but found no access manager contract address attached to it. The revoke-role call cannot be encoded without a target contract. | Verify that the system has a deployed access manager. If the system was recently bootstrapped, confirm the indexer has caught up before retrying. | | `DALP-0217` | permission | 403 | no | One or more role names in the request did not match any known system access control role. The platform resolves each role by field name before encoding the on-chain call. | Check the role value against the list of supported role names and correct any typos or unsupported values. | | `DALP-0218` | client | 400 | no | The platform selected the `grantMultipleRoles` encoding path (one address, multiple roles) but the resolved address was unexpectedly absent after deduplication. This reflects an internal state inconsistency rather than a caller error. | Retry the request. If the problem persists, contact support with the request id. | | `DALP-0219` | permission | 403 | no | The platform selected the single `grantRole` or `revokeRole` encoding path (one address, one role) but the resolved address or role was unexpectedly absent. This reflects an internal state inconsistency rather than a caller error. | Retry the request. If the problem persists, contact support with the request id. | | `DALP-0220` | permission | 403 | no | The platform selected the `batchGrantRole` or `batchRevokeRole` encoding path (multiple addresses, one role) but the resolved role was unexpectedly absent. This reflects an internal state inconsistency rather than a caller error. | Retry the request. If the problem persists, contact support with the request id. | | `DALP-0221` | operational | 500 | no | The platform found an event record in the activity log where all three sender fields (`senderAddress`, `accountAddress`, and `contractAddress`) are null. The activity list cannot build a response item without a sender address. | Contact support with the request id. This indicates an indexer event record is missing expected address data. | | `DALP-0222` | dependency | 503 | yes | The addon factory create route reached its execution step but the system context was not populated. The route requires system middleware to run before the handler. | Contact support with the request id. This indicates a server configuration issue with middleware ordering. | | `DALP-0223` | permission | 403 | no | The paymaster-signer addon initialization step needs a database connection to acquire an advisory lock before staging the signer key. The database context was not present at that point. | Contact support with the request id. This indicates a server configuration issue with database middleware ordering. | | `DALP-0224` | dependency | 503 | yes | The paymaster-signer initialization step queries the indexer for the ERC-4337 EntryPoint address, but the database context was unavailable or the EntryPoint record was not found. | Retry after verifying the account abstraction deployment module ran and the indexer is synced. Contact support if the issue continues. | | `DALP-0225` | dependency | 503 | yes | The PriceResolver addon initialization needs the FeedsDirectory contract address from the indexer. The database context was unavailable when the platform tried to resolve this prerequisite. | Retry after confirming the feeds directory is deployed and the indexer has indexed it. Contact support if the issue continues. | | `DALP-0226` | operational | 500 | no | The platform could not complete the on-chain addon registration. This can happen when the system access manager is unavailable, the addon type is unsupported for the encoding step, or the system's addon registry predates instance-implementation wiring and cannot install factory-kind addons. | Check that the system is fully bootstrapped and the addon registry is up to date. Contact support with the request id if the problem persists. | | `DALP-0227` | client | 404 | no | The platform looked up the addon factory by its on-chain address in the indexer and found no matching record. The factory may not yet be indexed or the address is not registered on this system. | Confirm the factory address is correct and that the indexer has processed the registration transaction. Retry after the indexer catches up. | | `DALP-0228` | domain | 409 | no | The addon registration transaction was confirmed on-chain, but the transaction receipt logs did not include the expected `SystemAddonRegistered` event. Without that event the platform cannot determine the deployed addon proxy address. | Contact support with the request id. The deployment may have succeeded but the receipt log is missing expected event data. | | `DALP-0229` | client | 400 | no | All addon registration transactions completed and receipts were returned, but none of the receipts carried a `blockNumber`. The platform requires a block number to mark the registration as indexed and return a finalized result. | Contact support with the request id. This indicates an unexpected chain or receipt format issue. | | `DALP-0230` | permission | 403 | no | The paymaster addon deployed on-chain but the transaction produced no receipt. Without a receipt the platform cannot decode the deployed proxy address from the event logs, so the staged signer key cannot be bound to the new paymaster. | Contact support with the request id. The on-chain transaction may have succeeded; support can locate the proxy address and manually complete the signer binding. | | `DALP-0231` | permission | 403 | no | The staged signer key in the secrets store does not match the signer registered on-chain for the paymaster proxy at `{paymasterAddress}`. This happens when a prior partial deploy left a stale or missing key, or when the staged key is a legacy raw private key that the platform refuses to bind. | Use the paymaster signer rotation endpoint to replace the signer key with a valid custody-backed key, then retry the addon registration. | | `DALP-0232` | permission | 403 | no | The platform found a value in the pending signer key slot for `{paymasterAddress}` but the value is not a valid hexadecimal wallet identifier. This typically indicates corrupted or truncated data written by a previous provisioning attempt. | Contact support with the request id. The pending key entry must be cleared and the paymaster signer re-provisioned via the rotation endpoint. | | `DALP-0233` | operational | 500 | no | The PriceResolver addon was included in a batch deployment request, but the required FeedsDirectory address and price topic ID were not pre-fetched before the deployment loop started. The platform requires these values to initialize the resolver correctly. | Ensure the system has a deployed FeedsDirectory and that the indexer has recorded it before requesting a PriceResolver addon deployment. | | `DALP-0234` | client | 404 | no | The system does not have a deployed addon registry. The platform requires an addon registry to be present before any addon can be created or registered. | Complete the system bootstrap to deploy the addon registry, confirm the indexer has caught up, then retry the addon creation request. | | `DALP-0235` | permission | 403 | no | The paymaster addon deployed on-chain, but the platform could not reach the secrets store to record the paymaster signer key. Without this step the paymaster proxy has no signer key binding and cannot sponsor transactions. | Contact support with the request id. The platform's secrets service must be available to complete paymaster signer key binding after deployment. | | `DALP-0236` | permission | 403 | no | The platform attempted to stage a new paymaster signer key before deployment but could not reach the secrets store. The signer key must be staged before the on-chain deploy so the workflow can bind it to the proxy address afterward. | Contact support with the request id. The platform's secrets service must be available before a paymaster addon deployment can begin. | | `DALP-0237` | permission | 403 | no | The platform attempted to reconcile the staged signer key against an existing paymaster proxy but could not reach the secrets store. Reconciliation reads the pending key to verify it matches the on-chain signer before allowing retry or re-deployment. | Contact support with the request id. The platform's secrets service must be available to complete paymaster signer key reconciliation. | | `DALP-0238` | dependency | 503 | yes | The addon factory create route requires a workflow execution client to submit durable on-chain transactions, but the client was not present in the request context. This indicates a server configuration problem, not a request data problem. | Contact support with the request id. This indicates the `restateMiddleware` is missing from the route composition on the server. | | `DALP-0239` | dependency | 503 | yes | The bundler balance endpoint requires the organization's bundler EOA wallet address to be stored in settings, but no value has been recorded for `BUNDLER_WALLET_ADDRESS`. | Set `BUNDLER_WALLET_ADDRESS` in the organization settings, then retry the request. | | `DALP-0240` | operational | 500 | no | The topic create route delegates the on-chain transaction to the transaction queue, which requires HTTP request headers to build the idempotency key. The headers were absent from the request context. | Contact support with the request id. This indicates the route was invoked without standard HTTP request headers, which is a server configuration problem. | | `DALP-0241` | operational | 500 | no | The topic delete route delegates the on-chain transaction to the transaction queue, which requires HTTP request headers to build the idempotency key. The headers were absent from the request context. | Contact support with the request id. This indicates the route was invoked without standard HTTP request headers, which is a server configuration problem. | | `DALP-0242` | client | 404 | no | The platform queried the indexer's topic scheme registry and found no topic registered under the name `{topicId}`. The topic may not have been created, or the indexer may not have caught up with a recent creation transaction. | Verify the topic name is correct and that the topic was successfully created. If the topic was recently created, wait for the indexer to catch up and retry. | | `DALP-0243` | operational | 500 | no | The topic update route delegates the on-chain transaction to the transaction queue, which requires HTTP request headers to build the idempotency key. The headers were absent from the request context. | Contact support with the request id. This indicates the route was invoked without standard HTTP request headers, which is a server configuration problem. | | `DALP-0244` | operational | 500 | no | An internal queue bridge function expected `cachedResult` to be populated by the `startWorkflow` callback before reading it, but the value was absent. This is a platform-level programming error, not a problem with the request. | Contact support with the request id and the route name. This error indicates a defect in the platform's transaction queue bridge. | | `DALP-0245` | client | 404 | no | The platform checked the system's indexed state and found no compliance contract deployed. The compliance module uninstall operation requires a compliance contract to be present. | Confirm the system bootstrap completed successfully and that the compliance contract is deployed and indexed. Retry after the indexer catches up. | | `DALP-0246` | client | 404 | no | The platform looked up the compliance module type names in the indexed directory tables but found no registered implementation address for the requested type(s). This happens when the caller provides module types by name without an explicit implementation address and the on-chain directory has not yet been indexed. | Supply the `implementation` address directly in the request body, or wait for the directory indexer to catch up and retry. | | `DALP-0247` | client | 404 | no | The platform checked the compliance module registry for the given module address and found no matching entry. The module must be registered before it can be uninstalled. | Confirm the module address is correct and that it appears in the system's compliance module registry before calling this operation. | | `DALP-0248` | operational | 500 | no | The platform located the compliance module and resolved its instance address, but the on-chain binding lookup returned an unexpected state (module not found or multiple bindings) that prevents uninstall from proceeding. | Verify the module is in an active or disabled binding state on-chain. If the problem continues, contact support with the request id. | | `DALP-0249` | operational | 500 | no | The platform attempted to read the on-chain directory but no directory contract address is configured for the active network. This indicates a server-side configuration gap rather than a caller error. | Contact support with the request id; the platform needs the directory contract address configured for this network before the operation can proceed. | | `DALP-0250` | client | 404 | no | The platform queried the on-chain directory but no system factory address is recorded for this network. The directory may not yet be indexed or the factory was never registered. | Confirm the system factory contract is deployed and registered in the directory, and that the indexer has processed the registration block before retrying. | | `DALP-0251` | client | 400 | no | The platform could not resolve a system address for the organization because neither the request body nor the organization's stored configuration contains one. | Include a system address in the request, or ensure the organization has a system address configured before calling this operation. | | `DALP-0252` | operational | 500 | no | The platform's internal workflow bridge reached the result-read step without a cached workflow result, which means the workflow start step did not complete as expected. This is an internal platform error, not a caller error. | Retry the operation. If the problem persists, contact support with the request id and the operation name. | | `DALP-0253` | operational | 500 | no | The platform's identity creation workflow returned without a transaction receipt in the cached result, which means the queue bridge did not complete the workflow start step correctly. This is an internal platform error. | Retry the operation. If the problem persists, contact support with the request id and the operation name. | | `DALP-0254` | operational | 500 | no | The platform validated the claim topic and data but the claim value failed an auto-claim business rule check specific to the topic type. For example, a boolean auto-claim topic rejected the supplied value. | Review the claim data for the topic named in the request and correct the value to satisfy the topic's validation rules before retrying. | | `DALP-0255` | operational | 500 | no | The platform's claim issue route reached the `knowYourCustomer` claim validation step but the system context was not loaded by the middleware chain. This is an internal server configuration error. | Contact support with the request id; the route is missing the system middleware required for this claim topic. | | `DALP-0256` | dependency | 503 | yes | The platform reached an identity mutation route but the system context was not populated by the middleware chain. The request cannot proceed without a resolved system. | Contact support with the request id; this indicates a route composition or middleware ordering issue on the server. | | `DALP-0257` | operational | 500 | no | The platform's claim issue route reached the `knowYourCustomer` claim validation step but the database context was not available. This is an internal server configuration error. | Contact support with the request id; the route is missing the database middleware required for this claim topic. | | `DALP-0258` | dependency | 503 | yes | The platform reached an identity operation but the database context was not populated by the middleware chain. The request cannot proceed without a database connection. | Contact support with the request id; this indicates a route composition or middleware ordering issue on the server. | | `DALP-0259` | domain | 409 | no | The platform checked the identity key registry and found no `MANAGEMENT_KEY` entry for the caller's signing wallet on the target identity. Claim revocation requires management rights on the identity. | Use a wallet that holds a `MANAGEMENT_KEY` on the target identity, or ask the identity owner to grant management rights before retrying. | | `DALP-0260` | client | 404 | no | The platform polled the indexed directory for the identity factory address and found none within the readiness window. The factory may not have been deployed or the indexer has not yet processed the registration block. | Confirm the identity factory is deployed and registered in the directory, wait for the indexer to catch up, then retry. | | `DALP-0261` | client | 400 | no | The platform attempted to normalize the provided address to lowercase and found it does not conform to the Ethereum address format. The value is not a valid 0x-prefixed 40-character hex string. | Provide a valid Ethereum address: a 0x-prefixed string of exactly 40 hexadecimal characters. | | `DALP-0262` | operational | 500 | no | The platform found more than one active, non-revoked claim for the same topic on this identity contract. Each topic should have at most one active claim, so this state indicates a data integrity issue the platform cannot resolve automatically. | Contact support with the request id and the identity address. The platform team will audit the duplicate claims and restore the expected single-claim state for this topic. | | `DALP-0263` | client | 400 | no | The identity contract at the given address exists in the system but has no linked wallet account. Issuing a `knowYourCustomer` claim requires the identity to have an associated account so the platform can match it against the approved KYC profile. | Verify that the target identity was fully deployed and linked to a wallet before issuing this claim. Use the identity read endpoint to confirm the `account` field is populated. | | `DALP-0264` | client | 404 | no | The platform could not find an identity contract associated with the given wallet address. The wallet has not completed the identity creation step, or the indexer has not yet recorded the deployed contract. | Confirm the wallet has completed identity creation before calling the register-pending endpoint. If creation finished recently, wait a moment for the indexer to process the block and then retry. | | `DALP-0265` | client | 404 | no | The platform could not locate an identity contract for the requested address. This occurs when the wallet has no registered identity in the current system, or when the wallet resolver cannot find a signing or executor wallet for the authenticated participant. | Verify the identity address belongs to an onboarded participant in this system. If the participant was recently created, allow a moment for the indexer to process the registration before retrying. | | `DALP-0266` | client | 404 | no | The platform looked up the requested system address in the indexer but found no matching system record. The address may be unknown or may belong to a different organization. | Confirm the system address is correct and belongs to your organization. If the system was recently deployed, wait for the indexer to process the deployment block and retry. | | `DALP-0267` | client | 404 | no | The platform submitted the identity creation transaction and it was confirmed on-chain, but the indexer did not index the resulting identity record within the allowed read-back window. No on-chain identity address was returned by the workflow to use as a fallback. | Retry the request. The identity was created on-chain and should become visible once the indexer catches up. If the problem persists, contact support with the request id. | | `DALP-0268` | client | 404 | no | The platform searched the identity registry for the given address but found no active registration. The identity may not exist, may have been removed, or may belong to a different registry. | Confirm the identity address is registered in the system's active identity registry. Use the identity read endpoint to check the registration status before retrying. | | `DALP-0269` | client | 404 | no | The platform found the identity contract but it is not registered in the current system's identity registry. A claim can only be revoked on an identity that is actively registered in the registry the system controls. | Register the identity in this system's identity registry before attempting to revoke claims. Use the identity registration endpoint if the identity contract already exists. | | `DALP-0270` | client | 404 | no | The platform located an identity contract for the wallet but its on-chain registration in the identity registry has not completed. The registration transaction may still be pending, or the identity may have been created without being registered. | Wait for the identity registration to complete and confirm the identity shows as registered before retrying. You can check status via the identity read endpoint. | | `DALP-0271` | operational | 500 | no | The platform validated the `knowYourCustomer` claim value against the participant's approved KYC profile and found a mismatch. The submitted claim value does not equal the content hash stored for the approved KYC version. | Retrieve the approved KYC content hash for the target participant and resubmit the claim with that exact value. Contact support with the request id if the approved hash is unclear. | | `DALP-0272` | client | 404 | no | The platform searched the registered topic schemes for the requested topic name and found no match. The topic may not exist in this system's claim-topics configuration. | Retrieve the list of registered claim topics via the claim-topics endpoint and use a topic name from that list. | | `DALP-0273` | domain | 422 | no | The target identity has no approved KYC profile, which topic '{topic}' requires before its claim can be issued. | Have the participant complete their KYC and a reviewer approve it, then issue the '{topic}' claim. | | `DALP-0274` | operational | 500 | no | The platform validated the `knowYourCustomer` claim payload and found that the value is not a plain string. This topic accepts only a single scalar string value as the claim data. | Resubmit the claim with a single string value in `claim.data.claim` instead of an array or object. | | `DALP-0275` | dependency | 503 | yes | The platform attempted to queue the identity creation transaction but the workflow execution client was not available. The transaction processing middleware was not applied to this route. | Contact support with the request id. This indicates a server-side configuration problem with the transaction processing service. | | `DALP-0276` | client | 400 | no | The platform confirmed exactly one active claim matched the revocation criteria, but the claim record was unavailable when the platform attempted to read it. This is a defensive guard against an unexpected internal state. | Retry the request. If the problem persists, contact support with the request id and the target identity address. | | `DALP-0277` | client | 404 | no | The platform checked whether the wallet has an identity contract and found it does not, or found no active registration targets for the wallet in the system's identity registry. The wallet has not been onboarded. | Onboard the wallet by creating an identity for it before performing this operation. Use the identity creation endpoint to register the participant. | | `DALP-0278` | client | 404 | no | The platform could not find a deployed system associated with the current organization. The organization may not have completed system deployment, or the system record may not yet be indexed. | Verify the organization has completed system setup and that the deployment has been indexed. Retry after the indexer processes the deployment. | | `DALP-0279` | client | 404 | no | The platform resolved the requested system address but found no matching system record in the indexer, and the address does not match this organization's configured system. The system address may be incorrect or belong to a different organization. | Confirm the system address is correct and belongs to your organization. Use the system read endpoint with `default` to retrieve the active system address for your organization. | | `DALP-0280` | dependency | 503 | yes | The paymaster list route ran without a system context. The system resolution middleware did not populate the system before the handler executed. | Contact support with the request id. This indicates a server-side configuration problem with the system middleware. | | `DALP-0281` | dependency | 503 | yes | The platform attempted to resolve the EntryPoint address from the network Directory contract, but the Directory contract address is not set in the network configuration. This prevents paymaster balance reads and smart-wallet approvals from proceeding. | Contact support with the request id. The network configuration is missing the Directory contract address required for account-abstraction operations. | | `DALP-0282` | client | 404 | no | The platform resolved the Directory contract address but found no EntryPoint registered in the indexer. The account abstraction deployment module registered an EntryPoint in the Directory, but the indexer has not yet processed that block. | Wait for the indexer to catch up with the chain, then retry. If the EntryPoint remains missing, verify that the AA deployment module completed registration in the Directory contract. | | `DALP-0283` | client | 404 | no | The platform could not find a paymaster with the given address in the indexed state for this system. The address may be incorrect, or the paymaster may not have been indexed yet. | Confirm the paymaster address is correct and that the indexer has processed the registration transaction. Use GET /v2/system/paymasters to list all paymasters currently indexed for this system. | | `DALP-0284` | client | 404 | no | The platform could not find a paymaster with the given address in the indexed state for this system. The address may be incorrect, or the paymaster registration may not yet be indexed. | Confirm the paymaster address is correct and that the indexer has processed the registration transaction. Use GET /v2/system/paymasters to list all paymasters currently indexed for this system. | | `DALP-0285` | client | 404 | no | The platform could not find a signer-type paymaster at the given address in the indexed state for this system. The address may be incorrect, the paymaster may belong to a different system, or it may not expose the sponsorship signer type. | Verify the paymaster address belongs to the current system and has the signer paymaster type registered. Use GET /v2/system/paymasters to list available paymasters. | | `DALP-0286` | permission | 403 | no | The authenticated user's session does not include a wallet ID, which the signer-key rotation route requires to identify the signing wallet. | Ensure the user account has a wallet provisioned and that the session token carries the wallet ID before calling this route. | | `DALP-0287` | dependency | 503 | yes | The token-factory route handler ran without a resolved system context, which is required to identify the token factory registry and proceed with factory operations. | Contact support with the request ID. This indicates a server-side middleware configuration issue. | | `DALP-0288` | client | 400 | no | The token factory deployment workflow completed and all transaction receipts were collected, but none of them recorded a block number. This prevents the platform from confirming the on-chain inclusion block. | Retry the request. If the problem continues, contact support with the request ID and the transaction hashes involved. | | `DALP-0289` | client | 404 | no | The platform could not find a registered token factory matching the requested type or factory address in the current system context. The factory may not have been deployed for this system. | Verify the factory type or address is correct and that the factory has been deployed and indexed for this system. Use GET /v2/system/factories to list available factories. | | `DALP-0290` | client | 404 | no | The platform queried the indexer for the factory at the given address but found no matching record. The system may not have finished bootstrapping, or the factory address is incorrect. | Confirm the factory address is correct and that the system bootstrap process completed successfully. Use GET /v2/system/factories to list indexed factories. | | `DALP-0291` | client | 404 | no | The platform found a contract at the given address in the indexer but its type is not a recognized factory type. The contract may have been deployed with an unsupported or unknown type identifier. | Verify the factory address refers to a supported token factory type. Use GET /v2/system/factories to list recognized factory types for this system. | | `DALP-0292` | dependency | 503 | yes | The token factory create route requires a transaction processing client to submit the durable factory deployment workflow. The service was not available in the current request context. | Contact support with the request ID. This indicates a server-side middleware configuration issue. | | `DALP-0293` | dependency | 503 | yes | The add-claim-topic and remove-claim-topic routes use a session advisory lock to serialize concurrent mutations on the same issuer. Async mode would release the lock before the on-chain write settles, risking a stale topic set on the next mutation. | Remove the `Prefer: respond-async` header and resend the request. These routes always return a synchronous result. | | `DALP-0294` | client | 404 | no | The platform searched the trusted-issuer registry (and its parent chain) in the indexer but found no entry for the given issuer address. The issuer may not have been registered, or the address may be incorrect. | Verify the issuer address is correct and that the issuer has been registered in the system's trusted-issuers registry. Use GET /v2/system/trusted-issuers to list registered issuers. | | `DALP-0295` | domain | 409 | no | Revoking this role would remove all accounts from the token's admin set. The platform requires at least one admin to remain so the token's access control can be managed after the operation. | Grant the admin role to another account before revoking it from the last current admin, or choose a different account to revoke. | | `DALP-0296` | client | 404 | no | The token's indexed state does not include an access control (access manager) record. Role operations require an access manager to be deployed and indexed for the token. | Verify that the token was deployed with an access manager and that the access manager address is indexed. Contact support if the token was recently deployed and the indexer may not have caught up. | | `DALP-0297` | permission | 403 | no | The request body did not match either of the two supported shapes for granting roles: one role to multiple accounts, or multiple roles to one account. | Restructure the request body to use exactly one of the two supported shapes: `{ accounts, role }` to grant one role to multiple accounts, or `{ account, roles }` to grant multiple roles to one account. | | `DALP-0298` | permission | 403 | no | The request body contained neither the `accounts`+`role` shape nor the `account`+`roles` shape, so the platform could not determine which accounts or roles to revoke. | Resubmit the request with exactly one of the two accepted shapes: `{ accounts, role }` to revoke one role from multiple accounts, or `{ account, roles }` to revoke multiple roles from one account. | | `DALP-0299` | permission | 403 | no | The `roles` array in the `{ account, roles }` grant request was empty, so the platform had no roles to grant. | Include at least one valid role name in the `roles` array and resubmit. | | `DALP-0300` | permission | 403 | no | The `roles` array in the `{ account, roles }` revoke request was empty, so the platform had no roles to revoke. | Include at least one valid role name in the `roles` array and resubmit. | | `DALP-0301` | permission | 403 | no | At least one name in the `roles` array did not resolve to a known access control role, so the platform rejected the entire request rather than apply a partial set of grants. | Verify every role name in the `roles` array against the list of valid access control roles and resubmit with corrected names. | | `DALP-0302` | permission | 403 | no | The role name `{role}` did not match any known access control role in the registry, so the platform could not encode the grant or revoke call. | Check the spelling of `{role}` against the list of supported access control roles and resubmit with a valid name. | | `DALP-0303` | operational | 500 | no | The burn handler encountered an unclassified failure before the transaction could be queued. This path is reached when neither a paused-token nor an insufficient-balance condition accounts for the failure. | Retry the request. If the error persists, contact support with the request id and the token address. | | `DALP-0304` | operational | 500 | no | The platform checked the indexed token state before encoding the burn calldata and found the token is currently paused on chain. Burn calls revert on paused tokens, so the request was stopped before submission. | Unpause the token using the token unpause endpoint, then resubmit the burn request. | | `DALP-0305` | domain | 409 | no | The authenticated participant has no on-chain identity contract registered with this system, which the claim-issue route requires to determine the issuer address. | Onboard the participant with an identity contract before issuing claims on their behalf. | | `DALP-0306` | domain | 409 | no | The authenticated participant has no on-chain identity contract registered with this system, which the claim-revoke route requires to determine the revoker address. | Onboard the participant with an identity contract before revoking claims on their behalf. | | `DALP-0307` | operational | 500 | no | The `assetClassification` topic requires a database lookup to resolve the on-chain asset class slug, but the database middleware was not active for this request path. | Contact support with the request id; this indicates a server configuration problem with the route's middleware chain. | | `DALP-0308` | operational | 500 | no | The platform could not find an OnchainID identity contract linked to this token. Claim operations require the token to have a deployed identity before claims can be issued or revoked. | Ensure the token was created with an identity contract attached. Contact support if the token was created correctly but the identity is not showing. | | `DALP-0309` | client | 404 | no | The topic name supplied in the claim request does not exist in the system's claim-topic scheme registry, so the platform cannot validate or issue the claim. | Query the list of registered claim topics for this system and resubmit with a topic name that appears in that list. | | `DALP-0310` | client | 404 | no | The compliance contract returned an empty binding list for the requested module type, meaning no module instance of that type is attached to this token. | Verify that a compliance module of the specified type has been bound to this token before encoding compliance arguments. | | `DALP-0311` | permission | 403 | no | The platform could not find the token in the indexed records for the current organization and system scope, either because the token is not yet indexed or belongs to a different system. | Confirm the token address is correct and that the indexer has processed the token's deployment. If it belongs to a different system, use the matching credentials. | | `DALP-0312` | operational | 500 | no | The token creation process reached a terminal failure before the platform produced a token. The failure reason is included in `{error}` and was not caused by an on-chain revert. | Inspect the `{error}` detail for the specific cause. If the issue persists, contact support with the request id. | | `DALP-0313` | operational | 500 | no | The token creation route requires database access to look up signing session and template data, but the database middleware was not active for this request. | Contact support with the request id; this indicates a server configuration problem with the route's middleware chain. | | `DALP-0314` | client | 404 | no | The platform could not locate a registered token factory for the requested token type, so it cannot proceed with token deployment. | Verify that the token type and optional factory address are correct, and that the system has completed bootstrapping with a factory for that type. | | `DALP-0315` | operational | 500 | no | The durable token-creation workflow reported a failed phase before producing a result; `data.phase` and `data.error` carry the on-chain or workflow-side failure reason. | Inspect `data.error` for the underlying revert or workflow message. Retry only if the cause is transient; otherwise surface the workflow error to the user. | | `DALP-0316` | client | 400 | no | The `dalp-asset` token type requires an instrument template to define its structure, but no `templateId` was included in the request. | Query the available instrument templates, select the appropriate one, and include its `templateId` in the token creation request. | | `DALP-0317` | dependency | 503 | yes | The workflow engine client was not initialised when the token creation route attempted to start the creation workflow, so the transaction could not be queued. | Retry the request after a short delay. If the problem persists, contact support with the request id. | | `DALP-0318` | operational | 500 | no | The authenticated participant does not have a deployed OnchainID identity on this system. Token creation requires the creating user to hold an identity so it can be recorded as the instrument owner. | Onboard the participant through the identity creation endpoint before attempting token creation. | | `DALP-0319` | client | 400 | no | The requested document has `holders` visibility, and the authenticated participant holds no role on this token, so the platform cannot serve the download URL. | Request the document with credentials for a participant who holds at least one role on this token, or ask the token administrator to assign an appropriate role. | | `DALP-0320` | operational | 500 | no | The requested document has `restricted` visibility. The platform checked the caller's token roles and found neither a governance nor an admin role on this token. | Use credentials for an account that holds a governance or admin role on this token, or request that an administrator share a non-restricted copy of the document. | | `DALP-0321` | operational | 500 | no | After the upload completed, the platform retrieved the stored object and found its byte length differs from the `fileSize` value supplied in the confirm-upload request. The orphaned object was removed from storage. | Re-upload the file and submit a confirm-upload request with the exact byte length of the file as reported by your file system. | | `DALP-0322` | client | 404 | no | The `replaceGroupId` supplied in the request does not match any existing document group for this token. No document with that group ID and `isLatest=true` exists in the platform records. | Confirm the `replaceGroupId` by listing the token's current documents, then resubmit with a valid group ID. | | `DALP-0323` | client | 404 | no | The document ID supplied does not match any non-deleted document record for this token. The document may have been deleted already or the ID may belong to a different token. | Verify the document ID against the token's active document list and resubmit with a valid ID. | | `DALP-0324` | client | 400 | no | The requested document type is not permitted for the token's asset type. Each asset type (for example, bond, equity) has a specific set of allowed document types. | Check the list of permitted document types for this token's asset type and resubmit with a compatible document type. | | `DALP-0325` | operational | 500 | no | The platform inserted the document metadata into the database but the insert returned no row, indicating a persistence failure. The orphaned object was removed from storage to avoid an inconsistent state. | Retry the confirm-upload request. If the error recurs, contact support with the request id and the object key. | | `DALP-0326` | client | 404 | no | The platform could not read the uploaded file at the expected storage location. The pre-signed upload may not have completed before the confirm step was called. | Re-upload the file using the pre-signed URL, confirm the upload completed successfully, then call the confirm step again. | | `DALP-0327` | client | 400 | no | The `objectKey` in the request does not start with the expected `token-documents/:tokenAddress/` prefix, or contains path traversal sequences (`..` or `//`). The platform rejects keys that fall outside the token's storage namespace. | Use the `objectKey` returned by the upload URL endpoint without modification. Do not alter the path prefix or add traversal sequences. | | `DALP-0328` | client | 404 | no | The `tokenFactory` filter value supplied to the token list query does not match any factory registered in the current system's token factory registry. | Retrieve the list of valid factory addresses for this system and use one of those values as the `tokenFactory` filter. | | `DALP-0329` | operational | 500 | no | A route that requires token feature data ran without the feature-loading middleware having populated that context. This indicates a server-side configuration problem. | Contact support with the request ID. This error points to a middleware ordering issue that requires a server-side correction. | | `DALP-0330` | dependency | 503 | yes | The platform looked up the `fixed-treasury-yield` feature row (denomination asset and treasury address) for this token but found no indexed record, or the record contains zero-address values. The platform's index has not yet processed the feature initialization event. | Retry after a short delay to allow the platform's index to process the feature initialization. If the error persists, contact support with the request ID. | | `DALP-0331` | dependency | 503 | yes | The platform looked up the `maturity-redemption` feature row for this token but found no indexed record. The platform's index has not yet processed the feature initialization event. | Retry after a short delay to allow the platform's index to process the feature initialization. If the error persists, contact support with the request ID. | | `DALP-0332` | client | 400 | no | The platform confirmed from indexed schedule data that fewer than one full interval has elapsed since the yield schedule's start date. No yield periods have completed, so there is nothing to claim. | Wait until at least one full yield interval has elapsed from the schedule start date, then retry the claim. | | `DALP-0333` | dependency | 503 | yes | The platform could not read the feature state for this token from the chain or the index. The chain node or a downstream data source returned an error. | Retry after a short delay. If the error persists, contact support with the request ID. | | `DALP-0334` | client | 400 | no | The requested freeze amount is larger than the holder's available (unfrozen) token balance. The platform checks the indexed balance before submitting the on-chain freeze. | Query the holder's current available balance and resubmit with an amount that does not exceed it. | | `DALP-0335` | operational | 500 | no | The platform found a base-price feed for this token, but the feed's last observed timestamp exceeds the maximum staleness window configured in the active PriceResolver policy. A stale feed is treated as absent to prevent serving outdated prices. | Ensure the price-feed provider is submitting updates within the policy's staleness window, then retry once a fresh observation is indexed. | | `DALP-0336` | operational | 500 | no | The platform decoded the indexed PriceResolver registration calldata and found it does not call `initialize()`. The registration event is malformed or references an incompatible contract version. | Verify that the PriceResolver addon was deployed and registered through the standard platform deployment flow. Contact support if the addon was deployed correctly. | | `DALP-0337` | operational | 500 | no | The platform decoded the `initialize()` calldata from the indexed PriceResolver registration but could not extract the feeds directory address from the expected argument position. The registration event is incomplete. | Verify that the PriceResolver addon was deployed with the correct initialization arguments. Contact support if the deployment appears correct. | | `DALP-0338` | client | 400 | no | The platform found a PriceResolver registration event in the index but the `initializationData` field does not contain a valid hex-encoded calldata value. The indexed event data is malformed. | Contact support with the request ID. Resolving this requires re-indexing the PriceResolver registration event. | | `DALP-0339` | dependency | 503 | yes | The platform retrieved a token record from the index but the data did not pass schema validation. The indexed record contains unexpected or missing fields. | Contact support with the request ID. This indicates a data integrity issue in the platform's index that requires investigation. | | `DALP-0340` | client | 404 | no | The platform could not find an indexed token at the supplied address within the current system's factory scope. The token may not be deployed, not yet indexed, or belong to a different system. | Verify the token address, confirm the token is deployed and indexed in the current system, then retry. | | `DALP-0341` | client | 400 | no | An address value supplied to the token features chain helper is not a valid Ethereum address. A valid address must be 0x-prefixed and contain exactly 40 hexadecimal characters. | Supply a correctly formatted Ethereum address (0x followed by 40 hex characters) and retry. | | `DALP-0342` | operational | 500 | no | The platform checked the indexed token state before encoding the mint calldata and found the token is currently paused on chain. Mint calls revert on paused tokens, so the request was stopped before submission. | Unpause the token using the token unpause endpoint, then resubmit the mint request. | | `DALP-0343` | permission | 403 | no | The platform queried the indexer for the token by address and found no record scoped to the authenticated system. The token is either not yet indexed or belongs to a different system. | Verify the token address is correct and that it has been deployed and indexed under the authenticated system. Retry once the indexer has processed the token. | | `DALP-0344` | client | 400 | no | The address supplied in the request body or parameters is not a valid Ethereum address. The platform requires a `0x`-prefixed, 40-character hex string. | Supply a checksummed or lowercase Ethereum address in the format `0x` followed by 40 hex characters and resend the request. | | `DALP-0345` | domain | 409 | no | The authenticated participant does not have an on-chain identity contract registered in the system. Setting a token price requires the caller to hold a valid identity. | Complete the onboarding flow for the participant to create their identity contract, then retry the set-price request. | | `DALP-0346` | operational | 500 | no | The platform looked up the `IssuerSignedScalarFeedFactory` addon address for this system and found none recorded. The feed infrastructure must be deployed before token prices can be submitted. | Deploy the feed system addon for this organization, then retry the set-price request. | | `DALP-0347` | dependency | 503 | yes | The token does not yet have an existing price feed and its symbol has not been indexed on this system. The platform needs the token symbol to construct a new feed description. | Confirm the token is enrolled on the current system and that the indexer has processed it, then retry the set-price request. | | `DALP-0348` | operational | 500 | no | The platform queried the indexed PriceResolver configuration and all available feed sources but could not locate a valid base-price feed for this token. Without a base price, currency conversion cannot proceed. | Register a base-price feed for the token in the configured feeds directory, then retry. | | `DALP-0349` | operational | 500 | no | After a mutation was submitted, the platform polled the token read endpoint to confirm the updated state was indexed. All retry attempts were exhausted without the token becoming available. | Retry the original mutation request. If the token state is visible in the API after a short wait, the mutation succeeded and only the readback confirmation failed. | | `DALP-0350` | operational | 500 | no | The bond has an active `maturity-redemption` feature. Redemptions for such bonds draw from the treasury address resolved by that feature, not from the bond contract balance. Transferring to the bond contract via this endpoint would not reach the redemption pool. | Use the maturity-treasury top-up endpoint to fund redemptions for this bond. | | `DALP-0351` | dependency | 503 | yes | The platform looked up the bond record for this token in the indexer and found no entry with a denomination asset set. The bond initialization transaction has not been processed yet. | Wait for the indexer to process the bond initialization block, then retry the top-up request. | | `DALP-0352` | operational | 500 | no | The redeem handler started but the token context was not populated, which means the token middleware did not run before the handler was reached. The redemption cannot proceed without knowing the token's current state. | Retry the request through the standard API path. If the error recurs, contact support with the request id and token address. | | `DALP-0353` | permission | 403 | no | The caller is attempting to redeem tokens on behalf of another address but does not hold the `custodian` role on this token. Only custodians may redeem on behalf of other holders. | Ask a token administrator to grant the `custodian` role to your address, or redeem only your own balance without specifying a different owner. | | `DALP-0354` | client | 400 | no | The caller specified a different owner address for the redemption, but the platform could not load the token permission context required to check delegation rights. | Retry the request. If the error persists, contact support with the request id. | | `DALP-0355` | client | 404 | no | The current system has no token sale addon registered. The list or read request requires at least one token sale addon to be installed on the system. | Install the token sale addon on the system before creating or querying token sales. | | `DALP-0356` | client | 404 | no | The system has no token sale addon registered in its addon registry. The create request requires the addon to be present before a sale contract can be deployed. | Install the token sale addon on the system through the system configuration, then retry the create request. | | `DALP-0357` | permission | 403 | no | The `systemAddon` filter address supplied in the request is not one of the token sale addon addresses registered under the authenticated system. | Use a `systemAddon` address from the list of addons returned by the system addons endpoint for the authenticated system. | | `DALP-0358` | operational | 500 | no | The `createTokenSale` transaction confirmed on-chain, but the platform found more than one token sale record in the index that matches the same transaction hash. This is a platform-side data inconsistency and cannot be resolved by retrying the same request. | Contact support and provide the request id, the transaction hash `{transactionHash}`, and the token address. The support team will reconcile the duplicate index entries and confirm the correct sale address. | | `DALP-0359` | dependency | 503 | yes | The token sale creation transaction was confirmed on-chain, but the indexer had not yet processed the event and returned a sale address within the wait window. | Retry the request with idempotency. The sale exists on-chain and will become available once the indexer catches up. | | `DALP-0360` | client | 400 | no | The `termsHash` value supplied in the request body is not a valid hex string. The platform requires it to be a `0x`-prefixed hexadecimal value. | Supply a `termsHash` as a `0x`-prefixed hex string, or omit it to use the default zero hash. | | `DALP-0361` | client | 404 | no | The token address does not appear as a registered identity in the system's identity registry. Token sale creation requires the token contract to be registered as an identity in the ERC-3643 registry. | Register the token as an identity in the system's identity registry before creating a sale for it. | | `DALP-0362` | client | 404 | no | The platform queried the indexer for a token sale at the given address and found no record. The sale may not have been deployed yet or the address may be incorrect. | Verify the sale address and confirm that the sale creation transaction has been indexed, then retry. | | `DALP-0363` | permission | 403 | no | The token sale exists in the indexer but its parent addon address is not registered under the authenticated system. The sale was created by a different system. | Confirm you are authenticating with the correct system credentials and that the sale address belongs to that system. | | `DALP-0364` | client | 400 | no | The token's registered identity record in the identity registry has a null country field. The token sale contract requires a country code to enforce investor eligibility rules. | Update the token's registered identity to include a valid country code before creating the sale. | | `DALP-0365` | operational | 500 | no | The `TransferApprovalComplianceModule` attached to this token returned an empty list of approval authorities. The platform requires at least one authority to be registered before approvals or revocations can proceed. | Contact the token administrator to add at least one approval authority to the `TransferApprovalComplianceModule` for this token, then retry the operation. | | `DALP-0366` | operational | 500 | no | The request included multiple transfer items with `transferType` set to `transferFrom`. The platform supports batch transfers only for the standard transfer type; `transferFrom` must be submitted one operation at a time. | Split the batch into individual `transferFrom` requests, one per sender-recipient pair, and submit them separately. | | `DALP-0367` | operational | 500 | no | The request supplied only one of the two optional identity override fields. The platform treats `fromIdentityAddress` and `toIdentityAddress` as an all-or-nothing pair; providing just one creates an ambiguous identity resolution. | Either include both `fromIdentityAddress` and `toIdentityAddress` in the request body, or omit both and let the platform resolve identities from the wallet addresses. | | `DALP-0368` | client | 404 | no | The platform looked up the `fromWallet` address in the identity registry and found no registered identity for it. A wallet must be onboarded and registered before it can be used as the sender in a transfer-approval operation. | Onboard the wallet through the identity registration flow, confirm the registry has indexed the new entry, then retry the request. | | `DALP-0369` | permission | 403 | no | The platform checked the `TransferApprovalComplianceModule`'s configured approval authorities and the sender's identity address was not in that list. Only identities explicitly added as approval authorities can approve or revoke transfer approvals on this token. | Ask the token administrator to add your identity address to the `TransferApprovalComplianceModule`'s approval authority list, then retry. | | `DALP-0370` | client | 400 | no | The platform parsed the address field in the transfer-approval request and found it was not a valid Ethereum address. A valid address starts with `0x` followed by exactly 40 hexadecimal characters. | Supply the correct Ethereum address (0x-prefixed, 40 hex characters) for the address field and retry. | | `DALP-0371` | client | 400 | no | The platform processed a `transferFrom` transfer request but the first transfer item contained no `from` address. The `from` field is required for `transferFrom` so the platform knows which address to deduct tokens from. | Include the `from` address in the transfer item when using the `transferFrom` transfer type, then retry. | | `DALP-0372` | client | 400 | no | The platform attempted to process a single-item transfer request but found no transfer items in the `transfers` array after passing the batch-size check. At least one transfer item is required. | Provide at least one transfer item in the `transfers` array and retry. | | `DALP-0373` | permission | 403 | no | The platform expanded the forced-transfer item list but the first item was missing the owner address, recipient address, or amount. All three fields are required to encode a `forcedTransfer` contract call. | Ensure each forced-transfer item includes `owner`, `recipient`, and `amount`, then retry. | | `DALP-0374` | client | 404 | no | The platform queried the indexer for the token at `{address}` but found no record. The token may not have been deployed, or the indexer has not yet processed the deployment block. | Confirm the token address is correct, that the token contract has been deployed, and that the indexer has processed the deployment block. Retry after indexing catches up if the deployment is recent. | | `DALP-0375` | operational | 500 | no | The token at `{tokenAddress}` is currently paused on-chain. The platform blocks all transfers while a token is in the paused state. | Unpause the token using the token pause management endpoint, then resubmit the transfer. | | `DALP-0376` | client | 404 | no | The platform looked up the `toWallet` address in the identity registry and found no registered identity for it. A wallet must be onboarded and registered before it can be used as the recipient in a transfer-approval operation. | Onboard the wallet through the identity registration flow, confirm the registry has indexed the new entry, then retry the request. | | `DALP-0377` | dependency | 503 | yes | The platform attempted to enqueue a transfer or forced-transfer transaction but the durable workflow service was not reachable. This indicates a service availability problem, not a problem with the request itself. | Retry the request after the service recovers. If the problem persists, contact support with the request id. | | `DALP-0378` | dependency | 503 | yes | The platform read the `TransferApprovalComplianceModule` configuration from the indexer but could not decode the module address or approval-authority parameters. The indexed compliance state is absent or inconsistent. | Trigger a re-index of the token's compliance state, or verify the module is correctly configured on-chain. Retry after the indexer has processed the latest compliance events. | | `DALP-0379` | client | 404 | no | The platform checked the identity registry for the sender's wallet and found no registered identity. The executing wallet must be onboarded before it can approve token transfers. | Onboard the wallet through the identity registration flow, confirm the registry has indexed the entry, then retry the approve-transfer request. | | `DALP-0380` | client | 404 | no | The platform checked the identity registry for the sender's wallet and found no registered identity. The executing wallet must be onboarded before it can revoke token transfer approvals. | Onboard the wallet through the identity registration flow, confirm the registry has indexed the entry, then retry the revoke-transfer-approval request. | | `DALP-0381` | operational | 500 | no | The platform looked up transaction `{transactionHash}` and found it is already in a terminal state (`COMPLETED`, `FAILED`, `DEAD_LETTER`, or `CANCELLED`). Force-fail applies only to transactions still in progress. | Check the current transaction state before retrying. If a reset is needed, contact support with the transaction id. | | `DALP-0382` | dependency | 503 | yes | The platform received a transaction hash from the durable workflow service that is not a valid `0x`-prefixed hex string. This indicates the workflow produced an unexpected result format. | Retry the request. If the problem persists, contact support with the request id so the workflow output can be inspected. | | `DALP-0383` | client | 404 | no | The platform could not locate a transaction with that id in the queue or ownership scope. Transactions belonging to another organization's wallets are reported the same way as genuinely missing ones to prevent enumeration. | Verify the transaction id is correct and belongs to your organization's wallets. If the transaction was recently created, retry after a short delay to allow processing. | | `DALP-0384` | client | 404 | no | The platform checked both the queue store and the chain provider for `{transactionHash}` and found no record in either place. The hash does not match any pending or confirmed transaction visible to this organization. | Confirm the transaction hash is correct and that the transaction was submitted through this platform. If the hash came from an external source, check the chain explorer directly. | | `DALP-0385` | client | 400 | no | The platform read a timestamp field from the stored transaction record and could not parse it into a valid date. This indicates the stored value is malformed. | Contact support with the request id and transaction hash. This is a data integrity issue the platform must resolve. | | `DALP-0386` | operational | 500 | no | Force-retry is available only for transactions in `FAILED` or `DEAD_LETTER` state. The transaction is currently in a different state, or its state changed between the check and the update. | Check the current transaction state via `GET /v2/transaction-requests/:transactionId/status`. Submit the force-retry request only when the state is `FAILED` or `DEAD_LETTER`. | | `DALP-0387` | client | 400 | no | The KYC action request identified by `requestId` does not have a linked KYC version. The platform requires a version association to look up the participant and verify ownership before marking the request as fulfilled. | Verify the action request record is complete and that a KYC version was created for it. If the record appears correct, contact support with the request id. | | `DALP-0388` | domain | 409 | no | The KYC profile version is not in the `under_review` state. The approval route reads the version with a row lock and checks its status before transitioning it to `approved`. | Submit a KYC version for review first (`POST /v2/kyc-profile-versions/:versionId/submissions`), then retry the approval once the version reaches `under_review` status. | | `DALP-0389` | domain | 409 | no | The KYC action request is not in the `open` state. The fulfill route checks the request status before marking it fulfilled, and the request has already been fulfilled or cancelled. | Verify the current status of the action request before retrying. Only `open` action requests can be fulfilled. | | `DALP-0390` | domain | 409 | no | The KYC profile version is not in the `under_review` state. The rejection route reads the version with a row lock and checks its status before transitioning it to `rejected`. | Confirm the version is currently `under_review` before calling the rejection endpoint. A version that is already approved, rejected, or still a draft cannot be rejected. | | `DALP-0391` | domain | 409 | no | The KYC profile version is not in the `draft` state. The submit route reads the version with a row lock and checks its status before transitioning it to `under_review`. | Confirm the version status is `draft` before submitting. A version that is already `under_review`, `approved`, or `rejected` cannot be submitted again. | | `DALP-0392` | domain | 409 | no | The KYC profile version is not in the `draft` state. The update route reads the version with a row lock and rejects writes to any version that has already been submitted for review, approved, or rejected. | Create a new draft version to make further changes, or check whether the existing draft can be cloned from the approved version. | | `DALP-0393` | client | 404 | no | The platform could not find a KYC document record matching the requested `documentId` for the given `versionId`. The document may have been deleted, or the document and version identifiers may not belong to the same KYC profile version. | Verify the `documentId` and `versionId` are correct and belong to the same version. List the documents on the version to confirm which records exist. | | `DALP-0394` | domain | 409 | no | The KYC profile version containing this document is not in the `draft` state. Documents can only be removed while the version is editable. | Documents attached to versions that are under review, approved, or rejected cannot be deleted. Create a new draft version if the documents need to change. | | `DALP-0395` | domain | 409 | no | The KYC profile version targeted by this upload is not in the `draft` state. The upload route checks the version status after acquiring a row lock and rejects the operation for any non-draft version. | Create a new draft version before uploading documents, or confirm the version is still in `draft` status before retrying. | | `DALP-0396` | operational | 500 | no | The platform completed the state-transition check but the database write to mark the version as approved returned no result. This is an internal storage error, not a problem with the version data. | Wait a moment and retry the approval request. If the error persists, contact support with the request ID and the version ID. | | `DALP-0397` | operational | 500 | no | The platform updated the version's review outcome to `changes_requested` but the follow-up write to record the update request returned no result. The version state was partially updated before the failure. | Retry the request-update call. If the error persists, contact support with the request ID and the version ID. | | `DALP-0398` | operational | 500 | no | The file was uploaded to object storage successfully, but the platform could not write the document metadata record to complete the upload confirmation. The orphaned file in storage is cleaned up automatically. | Re-upload the document and retry the confirm-upload call. If the error persists, contact support with the request ID and the version ID. | | `DALP-0399` | operational | 500 | no | The platform attempted to create or load the KYC profile container for this user but could not retrieve the profile record after the upsert. This is an internal storage error. | Retry the request. If the error persists, contact support with the request ID and the user ID. | | `DALP-0400` | operational | 500 | no | The platform inserted or confirmed the KYC profile container but could not retrieve the locked profile row needed to proceed with version creation. This is an internal storage error. | Retry the create-version request. If the error persists, contact support with the request ID and the user ID. | | `DALP-0401` | operational | 500 | no | The platform attempted to insert a new draft version record but the write returned no result. The profile container exists and version data was prepared; only the final version insert failed. | Retry the create-version request. If the error persists, contact support with the request ID and the user ID. | | `DALP-0402` | operational | 500 | no | The platform determined that the user's latest KYC version is not a draft and tried to create a new draft, but the insert returned no result. Existing version data is unchanged. | Retry the upsert request. If the error persists, contact support with the request ID and the user ID. | | `DALP-0403` | operational | 500 | no | The platform completed the state-transition check but the database write to mark the version as rejected returned no result. This is an internal storage error, not a problem with the version data. | Wait a moment and retry the rejection request. If the error persists, contact support with the request ID and the version ID. | | `DALP-0404` | operational | 500 | no | The platform verified the update request is open and belongs to the authenticated user but the write to set it as fulfilled returned no result. The request status is unchanged. | Retry the fulfill request. If the error persists, contact support with the request ID. | | `DALP-0405` | operational | 500 | no | The platform detected changed field values and attempted to update the existing draft version in-place, but the write returned no result. The draft content is unchanged. | Retry the upsert request with the same data. If the error persists, contact support with the request ID and the user ID. | | `DALP-0406` | operational | 500 | no | The platform created a new draft version record but the subsequent write to record it as the profile's latest version returned no result. The new version exists but is not yet linked to the profile. | Retry the upsert request. If the error persists, contact support with the request ID and the user ID. | | `DALP-0407` | operational | 500 | no | The platform validated the requested state transition but the database write to update the version record returned no result. This can happen during a submit-for-review or a changes-requested step. | Retry the operation. If the error persists, contact support with the request ID and the version ID. | | `DALP-0408` | operational | 500 | no | The platform confirmed the version is a draft and prepared the field changes, but the database write to apply them returned no result. No fields were modified. | Retry the update request with the same fields. If the error persists, contact support with the request ID and the version ID. | | `DALP-0409` | client | 404 | no | The legacy v1 document confirm-upload route tried to stat the object at the provided `objectKey` in the organization's storage bucket, but the object does not exist. The pre-signed upload to object storage did not complete before confirm-upload was called. | Re-upload the file to object storage using a fresh pre-signed URL, verify the upload succeeds, then call confirm-upload again with the same `objectKey`. | | `DALP-0410` | client | 400 | no | The provided `objectKey` does not start with the expected prefix `kyc/<participantId>/<versionId>/` for this version. The legacy v1 confirm-upload route validates the key prefix against the locked version row before registering the document. | Use only `objectKey` values returned by the pre-signed upload endpoint for this version. Keys scoped to a different participant or version are rejected. | | `DALP-0411` | client | 404 | no | The platform found the KYC profile record for this user but the profile has no linked `latestVersionId`, so the join to `kycVersions` returned no row. The user has a profile container but has never created or submitted a KYC version. | Check whether the user has a KYC version in progress via `GET /v2/kyc-profiles/:userId`. If no version exists, create one before reading the KYC data. | | `DALP-0412` | client | 404 | no | The delete-returning query found no KYC profile row matching this user's participant identifier. The profile was either never created or has already been removed. | Confirm the user has a KYC profile before calling the delete endpoint. If the profile was already deleted, no further step is needed. | | `DALP-0413` | client | 400 | no | The create-version route was called without `initialData` and without a resolvable source version. The profile has no `approvedVersionId` or `latestVersionId` to clone from, and no `cloneFromVersionId` was supplied. | Pass `initialData` with the user's KYC fields when creating a first version for a new user, or supply a `cloneFromVersionId` that points to an existing version. | | `DALP-0414` | domain | 409 | no | The authenticated participant's `participantId` does not match the `participantId` on the KYC version associated with this action request. The fulfill route enforces that only the subject of the KYC review can mark their own action request as fulfilled. | Authenticate as the participant who owns the KYC version linked to this action request, then retry. | | `DALP-0415` | domain | 409 | no | The KYC profile version is not in the `under_review` state. The request-update route checks the version status after acquiring a row lock and rejects the operation for any version that is not currently being reviewed. | Confirm the version is in `under_review` status before requesting an update. Submit the version for review first if it is still a draft. | | `DALP-0416` | client | 404 | no | The platform found no KYC profile row for the requested `userId`. The user has not started the KYC process yet, or the profile was deleted. | Verify the `userId` is correct. If this is a new user, create a KYC version first (`POST /v2/kyc-profiles/:userId/versions`), which will initialize the profile automatically. | | `DALP-0417` | client | 404 | no | The fulfill handler resolved the KYC version linked to the action request but found no KYC profile for the participant who owns that version. The profile row is required to clear the pending-update flag after fulfillment. | Verify the action request ID and that the participant has a KYC profile. If the profile was deleted, create a new one before retrying. | | `DALP-0418` | client | 404 | no | The version-create handler resolved a source version ID to clone from (via `cloneFromVersionId`, `cloneFrom: approved`, or `cloneFrom: latest`) but the referenced version row no longer exists in the database. | Pass `initialData` directly in the request body to seed the new draft, or provide a valid `cloneFromVersionId` that still exists. | | `DALP-0419` | client | 404 | no | The document upload confirmation handler looked up the KYC version by the provided version ID under a database lock and found no matching row. The version ID may be wrong or the version may have been deleted. | Verify the version ID used in the upload confirmation request. If the version was deleted, start a new upload flow with a valid draft version. | | `DALP-0420` | client | 404 | no | The fulfill handler queried the KYC version linked to the action request's `versionId` and found no matching row. The version may have been deleted after the action request was created. | Verify the action request still has a valid associated KYC version. If the version no longer exists, the action request cannot be fulfilled. | | `DALP-0421` | client | 404 | no | The version read handler queried the KYC version by the provided version ID and found no matching row. The version ID may be wrong, belong to a different organization, or the version may not exist yet. | Verify the version ID and confirm the version belongs to the authenticated organization before retrying. | | `DALP-0422` | operational | 500 | no | The KYC version was submitted for review between the time the file was uploaded and the time the upload confirmation arrived. The platform requires the version to be in draft status to accept new documents, so the uploaded file was removed from storage. | Check the current version status. If it is under review, no further document uploads are possible for this version. Start a new draft version if additional documents are needed. | | `DALP-0423` | client | 400 | no | The password-reset route looked up the target user within the authenticated organization and found that the user account has no email address stored. The platform needs an email address to send the reset link. | Ensure the user account has a verified email address before triggering a password reset. | | `DALP-0424` | client | 404 | no | The platform could not find a participant with the given ID in the authenticated organization. The participant may not exist or may not be a member of this organization. | Verify the participant ID and confirm the participant is a member of the current organization. | | `DALP-0425` | client | 404 | no | The platform searched for a participant whose wallet matches the provided address within the authenticated organization and found no match. The wallet may not be registered, or it belongs to a participant outside this organization. | Verify the wallet address and confirm the wallet is associated with a participant in the current organization. | | `DALP-0426` | client | 404 | no | The security read handler could not locate the target user within the authenticated organization. The user may not exist, may not be a member of this organization, or the session has no active organization context. | Verify the user ID and confirm the user is a member of the organization the admin session is scoped to. | | `DALP-0427` | client | 404 | no | The platform searched the approved KYC versions in this organization for a participant with the given national ID and found no match. No participant has a currently approved KYC version carrying that national ID. | Verify the national ID value and confirm the participant has a KYC version in the approved state within this organization. | | `DALP-0428` | client | 404 | no | The password-reset handler could not locate the target user within the authenticated organization. The user may not exist, may not be a member of this organization, or the session has no active organization context. | Verify the user ID and confirm the user is a member of the organization the admin session is scoped to. | | `DALP-0429` | client | 404 | no | The MFA reset handler could not locate the target user within the authenticated organization. The user may not exist, may not be a member of this organization, or the session has no active organization context. | Verify the user ID and confirm the user is a member of the organization the admin session is scoped to. | | `DALP-0430` | dependency | 503 | yes | The wallet-creation route requires a connection to the workflow engine to dispatch the wallet provisioning workflow, but the client was not initialized for this request. This is a platform-side configuration or connectivity issue. | Retry in a moment. If the problem continues, contact support with the request ID so the workflow engine connectivity can be investigated. | | `DALP-0431` | dependency | 503 | yes | The XvP create route submitted the settlement creation transaction and confirmed it on-chain, but the indexer did not produce the settlement row within the retry window. The indexed settlement is required to return the settlement ID and state to the caller. | Retry the request. If the settlement ID is needed immediately, query the indexer directly after a short delay. Contact support with the request ID if the problem persists. | | `DALP-0432` | dependency | 503 | yes | The indexer has not linked the fixed-yield schedule to its token metadata yet. | Retry after indexing catches up. | | `DALP-0433` | domain | 409 | no | The capital-raise-limit compliance module stores configuration that cannot be changed after the module instance has been installed. | Deploy a new capital-raise-limit module instance with the required parameters, then update token compliance to use that instance. | | `DALP-0434` | client | 400 | no | The token uses the legacy compliance model, which has no scoped module bindings and cannot atomically update module parameters with a scope. | Use configureComplianceModule for legacy tokens, or migrate the asset to a current compliance-engine token before configuring scoped modules. | | `DALP-0435` | client | 400 | no | The token uses the legacy compliance model, which supports only the single-instance compliance-module install flow. | Use installComplianceModule for legacy tokens, or migrate the asset to a current compliance-engine token before installing scoped module instances. | | `DALP-0436` | client | 400 | no | The token uses the legacy compliance model, which has no per-instance scope state to update. | Use legacy compliance-module configuration routes for legacy tokens, or migrate the asset to a current compliance-engine token before setting module scope. | | `DALP-0437` | dependency | 400 | no | A Workflow Engine endpoint returned HTTP 400 before Platform API could complete the downstream operation. | Retry only after verifying the API request shape and workflow input. If the request is valid, contact support with the request id. | | `DALP-0438` | dependency | 401 | no | A Workflow Engine endpoint returned HTTP 401, so Platform API could not authenticate the downstream workflow call. | Retry after the service credentials are corrected. If you are an API consumer, contact support with the request id. | | `DALP-0439` | dependency | 403 | no | A Workflow Engine endpoint returned HTTP 403, so the downstream workflow refused Platform API's call. | Retry after the workflow permissions or service identity are corrected. If you are an API consumer, contact support with the request id. | | `DALP-0440` | dependency | 404 | yes | A Workflow Engine endpoint returned HTTP 404, which means the expected workflow service, handler, or invocation target was not available. | Retry after the workflow deployment and service discovery have caught up. If it continues, contact support with the request id. | | `DALP-0441` | dependency | 409 | no | A Workflow Engine endpoint returned HTTP 409 because the downstream workflow state did not allow this call at this time. | Refresh the resource or deployment status, wait for the active workflow step to finish, then retry if the operation is still valid. | | `DALP-0442` | dependency | 422 | no | A Workflow Engine endpoint returned HTTP 422 because the downstream workflow accepted the call envelope but rejected its semantic input. | Verify the requested operation is valid for the current resource state. If the request is valid, contact support with the request id. | | `DALP-0443` | dependency | 500 | no | A Workflow Engine endpoint returned HTTP 500 while processing the downstream operation. | Retry if the operation is idempotent. If it continues, contact support with the request id so the workflow failure can be investigated. | | `DALP-0444` | dependency | 504 | yes | A Workflow Engine endpoint returned HTTP 504 before the downstream operation completed. | Check the resource or deployment status before retrying so you do not duplicate a workflow step that may still complete. | | `DALP-0445` | dependency | 400 | no | The transaction queue returned BAD\_REQUEST before a transaction could be accepted for processing. | Verify the route input, wallet verification payload, and queued transaction parameters before retrying. | | `DALP-0446` | dependency | 409 | no | The transaction queue returned CONFLICT because the requested transaction cannot be accepted in the current queue or resource state. | Refresh the transaction or resource state, wait for any active queued operation to finish, then retry if the operation is still valid. | | `DALP-0447` | dependency | 422 | no | The transaction queue accepted the operation envelope but rejected its semantic transaction input before dispatch. | Verify the requested chain operation is valid for the current contract and token state before retrying. | | `DALP-0448` | dependency | 504 | yes | The transaction queue did not observe the queued transaction confirmation before its timeout window expired. | Check the transaction status before retrying so you do not submit a duplicate operation. | | `DALP-0449` | client | 404 | no | The migration comparison route needs the active system address before it can compare deployed component implementations. | Set the SYSTEM\_ADDRESS setting or deploy a system, then retry the comparison. | | `DALP-0450` | client | 400 | no | The migration comparison route needs the directory contract address from the active network configuration. | Set networks.\.contracts.directory in config.yml for the default network, then retry the comparison. | | `DALP-0451` | dependency | 404 | yes | The directory contract address is configured, but the indexer has not produced the directory row needed for component comparison. | Retry after the indexer processes the directory registration. If it continues, contact support with the request id. | | `DALP-0452` | client | 400 | no | The migration start route needs an active organization before it can resolve the system and workflow scope. | Select an organization, then start the migration again. | | `DALP-0453` | client | 404 | no | The migration start route needs the active system address before it can submit the migration workflow. | Deploy a system or set the SYSTEM\_ADDRESS setting, then start the migration again. | | `DALP-0454` | auth | 403 | no | The migration start route needs the authenticated account wallet before it can verify migration permissions. | Connect a wallet to your account, then start the migration again. | | `DALP-0455` | auth | 403 | no | The authenticated wallet does not hold a role that is allowed to start the system migration workflow. | Use an account with the system manager or admin role, or ask an admin to grant the role before retrying. | | `DALP-0456` | client | 400 | no | The migration start route needs the directory contract address from the active network configuration. | Set networks.\.contracts.directory in config.yml for the default network, then start the migration again. | | `DALP-0457` | domain | 409 | yes | The migration workflow journal still has an active invocation for this organization. | Wait for the current migration to finish, then retry if another migration is still needed. | | `DALP-0458` | dependency | 500 | yes | Platform API could not reset the previous system migration workflow journal and state before submitting a fresh run. | Retry in a moment. If the problem continues, contact support with the request id. | | `DALP-0459` | client | 400 | no | The migration workflow needs a connected sender wallet and wallet id for the on-chain transactions. | Connect a wallet, then start the migration again. | | `DALP-0460` | dependency | 500 | no | The system migration workflow reported a terminal failure: `{reason}` | Review the failed migration step and retry after correcting the underlying issue. If it continues, contact support with the request id. | | `DALP-0461` | domain | 409 | yes | Another add/remove claim-topic mutation for this trusted issuer is already running. Platform API does not queue same-key callers behind the database lock because that can consume database pool sessions. | Wait for the active mutation to finish, then retry the claim-topic request if the issuer's topic set still needs to change. | | `DALP-0462` | domain | 422 | no | The template contains configured modules or required controls from a different compliance module generation. | Remove the incompatible controls or create a template with the matching legacy/current module set. | | `DALP-0463` | client | 409 | no | The organization already has a non-system template with the submitted name. | Choose a unique template name or update the existing template instead. | | `DALP-0464` | client | 404 | no | Platform API could not find an account with native-balance state in the active system scope. | Verify the chain ID, address, system selection, and indexer freshness before retrying. | | `DALP-0465` | client | 400 | no | The configured maturity-redemption treasury is a smart contract. ERC-20 `approve` must be called from the contract that owns the funds, which this route cannot do on its behalf. | Call `approve(spender, amount)` directly from the treasury contract (e.g. via its admin or governance flow), or reconfigure the feature to use an externally-owned treasury wallet. | | `DALP-0466` | client | 404 | yes | The maturity-redemption feature row for this token has not been created or the indexer has not processed the feature initialization yet, so denomination asset and treasury are still unset. | Verify the token has the maturity-redemption feature attached and wait for the indexer to catch up, then retry. | | `DALP-0467` | client | 403 | no | ERC-20 `approve` must be called from the wallet that owns the funds. The authenticated caller is not the configured treasury wallet, so this route cannot proxy the approval. | Retry signed in as the configured treasury wallet. | | `DALP-0468` | dependency | 503 | yes | The indexer populates `treasury_is_contract` via a single `eth_getCode` on every `MaturityRedemptionFeatureCreated` / `TreasuryUpdated`, but the column is still `null` for this feature. The indexer has not finished the classification step yet (typical during a partial reindex / backfill). Without that flag we cannot decide whether the approve flow is allowed (EOA treasuries) or must be blocked (contract treasuries), so we refuse to proceed rather than risk a misclassified on-chain failure. | Wait for the indexer to catch up and retry. If the column stays `null` for an extended period, verify the indexer is healthy and that `MaturityRedemptionFeatureCreated` / `TreasuryUpdated` for this feature were ingested. | | `DALP-0469` | client | 400 | no | The native-balance history endpoint limits each page to 100 rows to keep indexer queries bounded. | Request 100 or fewer history rows per page and use the pagination links for additional rows. | | `DALP-0470` | client | 400 | no | The native-balance history endpoint requires a lower block bound so history scans stay within the supported query window. | Include `filter[since]` with a block number using the `gte` or `eq` operator, then retry. | | `DALP-0471` | client | 404 | no | Platform API could not find an active (non-revoked) claim matching the requested topic on the target identity. | Verify the topic and identity address, and confirm the claim has not already been revoked, before retrying. | | `DALP-0472` | auth | 403 | no | The route requires a recent re-authentication and the current session is older than the policy window. | Re-authenticate (sign in again or complete the step-up challenge) and retry the request. | | `DALP-0473` | dependency | 503 | yes | The indexer populates `treasury_is_contract` via a single `eth_getCode` on every `FixedTreasuryYieldFeatureCreated` / `TreasuryUpdated`, but the column is still `null` for this feature. The indexer has not finished the classification step yet (typical during a partial reindex / backfill). Without that flag we cannot decide whether the approve-yield-allowance flow is allowed (EOA treasuries) or must be blocked (contract treasuries), so we refuse to proceed rather than risk a misclassified on-chain failure. | Wait for the indexer to catch up and retry. If the column stays `null` for an extended period, verify the indexer is healthy and that `FixedTreasuryYieldFeatureCreated` / `TreasuryUpdated` for this feature were ingested. | | `DALP-0474` | client | 409 | no | Compliance modules that price mint amounts in fiat (currently capital-raise-limit) require an IDALPPriceResolver addon registered on the system. The Platform API resolves the addon address server-side and injects it into the module's initialization payload. Without an installed addon there is no resolver to inject, so the deployment is refused before any on-chain transaction is queued. | Install the PriceResolver addon on this system (Addons → Price Resolver) before creating tokens whose compliance template includes capital-raise-limit, adding capital-raise-limit to an existing token, or updating its parameters. | | `DALP-0475` | domain | 409 | no | The platform-wide Account Abstraction feature flag is disabled, so smart wallets cannot be selected as default wallets for routed transactions. | Enable the platform Account Abstraction feature flag, or create the smart wallet without setting it as default. | | `DALP-0476` | domain | 409 | no | The platform-wide Account Abstraction feature flag is disabled, so smart wallets cannot be selected as default wallets for routed transactions. | Enable the platform Account Abstraction feature flag, or update only the smart wallet metadata. | | `DALP-0477` | domain | 409 | no | `conversion-minter` declares `dependsOn: ["conversion"]` in the addon registry. Publishing a template with the minter but no conversion would produce a runtime-not accepted token (a minter with nothing to mint into). | Add the missing dependency to `requiredFeatures` (or remove the orphan dependent), then retry the publish or update request. | | `DALP-0478` | dependency | 422 | yes | Before `redeem(amount)` runs, the Platform API handler reads `allowance(treasury, featureAddress)` on the denomination asset and compares it to the on-chain `calculatePayout(amount)` payout. The treasury is an externally-owned wallet and its ERC-20 allowance to the maturity-redemption feature contract is below that payout, so `TreasuryPayoutLib.payoutFrom` would revert with `ERC20InsufficientAllowance` inside the redeem transaction. The preflight refuses up front so the redeemer is not charged gas for a doomed tx. | Sign in as the configured treasury wallet (see `data.treasury`) and grant the maturity-redemption feature an allowance of at least `data.required` base units of the denomination asset via the bond's Manage maturity → Approve allowance control, then retry the redemption. Since ERC-20 `approve` overwrites (not adds), agents should submit `data.required` as the approve amount, not `data.required - data.allowance`. The error's `data` payload carries `allowance` and `required` as base-unit decimal strings, plus the `denominationAsset`, `feature`, and `treasury` addresses. | | `DALP-0479` | client | 422 | yes | The maturity-redemption feature's `isMatured` flag is still `false` and the on-chain `maturityDate` has not been reached, so `_MaturityRedemptionFeatureLogic.redeem` would revert with `BondNotYetMatured`. The preflight refuses up front so the redeemer is not charged gas for a doomed tx. | Wait until the configured `maturityDate` is reached and the bond is matured, or call `mature(token)` / `matureEarly(token, actualMaturityDate)` if you hold the maturity role and want to settle early. Retry once the feature is matured. | | `DALP-0480` | client | 409 | no | The name or slug collides with an existing asset class for this organization. | Choose a different name or use the existing asset class. | | `DALP-0488` | auth | 401 | no | The compliance webhook signature or URL token could not be verified against the provider credentials. | Verify the provider webhook URL and signing secret configuration, then send a freshly signed event. | | `DALP-0489` | client | 400 | no | The compliance webhook timestamp was more than five minutes away from the server clock. | Send a fresh provider event with a current timestamp and verify clock synchronization for the provider. | | `DALP-0490` | domain | 404 | no | A compliance webhook referenced an external subject ID that has not been mapped to a DALP identity or wallet. | Create the subject through DALP before accepting provider webhooks for that external ID, or reconcile the event from the audit log. | | `DALP-0491` | domain | 404 | no | The webhook target is not currently available for compliance event intake. | Verify the provider configuration and resume the provider before sending more provider events. | | `DALP-0492` | domain | 409 | no | The compliance provider failed provisioning or health checks and cannot process provider events. | Repair or reprovision the provider before retrying webhook processing. | | `DALP-0493` | domain | 422 | no | The provider payload did not match a supported ClaimSource verdict or monitoring-alert shape and was persisted for audit. | Review the provider event type and update the adapter mapping before replaying the event. | | `DALP-0494` | domain | 409 | no | The event timestamp or sequence is behind the last applied event for the same provider, subject, and topic. | Do not replay stale provider events; inspect the audit event if the provider's ordering guarantees appear broken. | | `DALP-0495` | dependency | 503 | yes | Platform API could not reach the provider health endpoint or the provider returned an unhealthy response. | Retry after a short backoff; if the failure persists, verify provider availability and provider credentials. | | `DALP-0496` | dependency | 502 | no | The provider applicant or monitored-subject creation call failed before DALP could persist the subject mapping. | Verify provider credentials and the submitted subject fields, then retry applicant creation. | | `DALP-0497` | contract | 502 | no | The tenant trusted issuer registry rejected the provider issuer EOA registration transaction. | Verify the provider issuer address, claim topic, tenant registry address, and transaction trace before retrying provisioning. | | `DALP-0498` | domain | 400 | no | The webhook payload declared a claim topic that is not configured on the provider. | Add the topic to the provider, or correct the provider adapter topic mapping. | | `DALP-0499` | domain | 404 | no | A wallet-subject compliance provider event referenced a wallet that DALP could not resolve to an OnchainID identity. | Register the wallet to an OnchainID identity before creating or replaying the compliance subject mapping. | | `DALP-0500` | domain | 410 | no | The pending webhook signing secret expired before it was promoted to the active secret. | Start a new secret rotation and update the provider dashboard with the active webhook signing secret. | | `DALP-0501` | client | 409 | no | The provider is not in a state that permits the requested operation (for example, resume requires paused; revoke is terminal). | Refresh the provider and choose an operation that matches its current state. | | `DALP-0502` | client | 404 | no | No compliance provider matching the requested ID exists within the calling organization. Cross-organization lookups are concealed and return the same response as an unknown provider ID. | Confirm the provider ID was created by and belongs to your organization, then retry the request. | | `DALP-0503` | client | 404 | no | No active topic matching the requested identifier exists on this compliance provider. Revoked topics are excluded from the default view and will also return this error unless the revoked include flag is set. | Verify the topic name and provider ID, confirm the topic has not been revoked, or add a new topic through the provider webhook endpoint. | | `DALP-0504` | client | 400 | no | The selected vendor product cannot attest the requested claim topic. | Choose one of the provider's supported topics or select a different provider kind. | | `DALP-0505` | client | 409 | no | Single-topic provider products have exactly one webhook; revoking it would leave the participant with no supported topics. | Revoke the compliance provider instead, or add another supported webhook before revoking this one. | | `DALP-0506` | contract | 502 | no | The on-chain identity factory rejected the claim-issuer participant identity deployment for the compliance provider. | Verify the system identity factory and signer configuration, then retry provisioning. The provider row stays in failed status until provisioning succeeds. | | `DALP-0507` | client | 429 | yes | The tenant has exhausted the replay-specific webhook rate-limit bucket. | Wait for the Retry-After interval before starting another replay. | | `DALP-0508` | client | 400 | no | The replay request spans more blocks or events than the API allows in a single replay job. | Split the replay into smaller ranges and retry. | | `DALP-0509` | domain | 409 | no | The endpoint is disabled and cannot accept live, replay, or test deliveries until it is re-enabled. | Re-enable the endpoint after fixing the delivery failure cause, then retry. | | `DALP-0510` | auth | 401 | no | The webhook signature, timestamp, or signed payload did not verify against the expected signing material. | Verify the signing secret, timestamp tolerance, and exact raw request body before retrying. | | `DALP-0511` | permission | 404 | no | The event does not exist or is not available to the current actor for recall. | Verify the event identifier and use an actor with webhook recall permissions. | | `DALP-0512` | client | 400 | no | The endpoint URL resolves to a private, loopback, link-local, or otherwise disallowed network range. | Use a publicly reachable HTTPS endpoint that does not resolve to a private network address. | | `DALP-0513` | domain | 409 | no | The tenant has reached the maximum number of webhook endpoints allowed for this environment. | Delete an unused endpoint or contact support to raise the tenant endpoint limit. | | `DALP-0514` | client | 409 | no | The same Idempotency-Key was previously used for a request with a different method, path, or body hash. | Reuse an Idempotency-Key only for the same request, or send a new key for a different request. | | `DALP-0515` | client | 409 | yes | Another request with the same Idempotency-Key is still being processed for this tenant. | Wait for the in-flight request to finish, then retry the same request. | | `DALP-0516` | client | 409 | no | The endpoint URL change cannot proceed silently, there are pending delivery attempts the dispatcher would re-target to the new URL. | Re-send the request with `?acknowledgePending=true` to confirm those deliveries should target the new URL, or wait for the queue to drain. | | `DALP-0517` | client | 422 | no | Switching an endpoint to `defaultPayloadShape='fat'` requires an explicit GDPR ceremony, the operator must acknowledge each `<eventType>.<fieldPath>` that the thin shape would have stripped. The ack on the request didn't cover every PII field for the endpoint's subscriptions, so the switch would have silently broadened the consent surface. | Resend the PATCH with `fatEventsAcknowledgment.fieldsAcknowledged` set to the full list of `<eventType>.<fieldPath>` paths returned by `getWebhookFatAcknowledgmentFields(subscriptions)`, the Console's switch-to-fat dialog computes this automatically. | | `DALP-0518` | dependency | 503 | yes | Platform API could not contact the Workflow Engine admin endpoint required to inspect or mutate workflow state. | Retry after a short backoff. If the problem continues, check the Workflow Engine cluster health and contact support with the request id. | | `DALP-0519` | client | 404 | no | The Workflow Engine admin API does not currently report a deployment matching the configured service URL. | Confirm the durable service is registered with Workflow Engine (force-redeploy if needed) and retry. | | `DALP-0520` | client | 409 | no | The workflow has an active invocation, has already succeeded, or its prior invocations could not be purged. | Inspect the workflow with the doctor route and resolve the blocking invocation before retrying. | | `DALP-0521` | dependency | 408 | yes | The Thales Luna 7 partition was waiting on out-of-band m-of-n approval and the configured retry window elapsed before the operator quorum signed off, so the workflow gave up. | Activate the partition on the HSM and re-submit the transaction. If expiries are frequent, lengthen the signing window via the signer config (luna.quorum.retryWindowMs). | | `DALP-0522` | dependency | 409 | no | The Luna vendor-extension reported the partition as activated, but the signing call still returned m-of-n-pending three times in a row. Either the firmware misreports activation or a concurrent caller is consuming the quorum. | Inspect the partition state on the HSM directly. If activation is genuinely pending, retry once the operator approves; otherwise contact support with the request id so the classification heuristic can be tuned. | | `DALP-0523` | domain | 422 | no | The token's transaction-fee rates have been permanently frozen on-chain. The mutation was rejected before reaching the queue. | Frozen rates cannot be modified. Update the fee recipient instead, or deploy a new token if different rates are needed. | | `DALP-0524` | permission | 404 | no | The requested participant cannot be selected by the authenticated session. | Remove the X-Participant header or retry with the authenticated participant id. | | `DALP-0525` | dependency | 502 | no | The provider transaction-registration call (Sumsub KYT) failed before DALP could persist the transaction-id mapping. | Verify provider credentials and the submitted transaction fields, then retry transaction registration. | | `DALP-0526` | client | 404 | no | No webhook endpoint with that identifier exists in the current tenant, or the endpoint has been deleted. Deleted endpoints remain as audit tombstones and are not available for new operations. | Verify the endpoint identifier belongs to the authenticated tenant. If the endpoint was deleted, create a new endpoint. | | `DALP-0527` | client | 404 | no | No delivery record matches the combination of delivery identifier, endpoint identifier, and tenant. On the receipt-create path, this also surfaces when the delivery's own `counterSignedReceipts` snapshot is false, meaning the feature was not enabled on the endpoint when that delivery was dispatched. | Confirm the delivery identifier and endpoint identifier are correct and belong to the authenticated tenant. List deliveries for the endpoint to retrieve valid identifiers. | | `DALP-0528` | client | 404 | no | No replay job with that identifier exists in the current tenant scope. | Verify the replay identifier and confirm it was created within the authenticated tenant. List replays for the endpoint to retrieve valid identifiers. | | `DALP-0529` | client | 404 | no | No receipt record with that identifier exists in the current tenant scope. | Verify the receipt identifier belongs to the authenticated tenant. Use the receipt list endpoint to retrieve valid identifiers. | | `DALP-0530` | client | 400 | no | The X-Executor header requested EOA execution for a participant type that cannot execute from an EOA. | Use X-Executor: smart-wallet or omit the header so the API selects the participant's supported executor. | | `DALP-0531` | client | 404 | yes | The X-Executor header requested smart-wallet execution, but no smart wallet is available for this participant and organization. | Wait for smart-wallet provisioning or indexing to complete, then retry. | | `DALP-0532` | domain | 409 | no | Mutually-exclusive token features bind to the same on-chain or accounting path and would either double-account the same transfer or contradict each other. The registry models these pairs so the publish path can reject them before a token is created from the template. | Remove one feature from each conflicting pair in `requiredFeatures`, then retry the publish or update request. | | `DALP-0533` | client | 404 | no | Platform API could not resolve the metadata payload from IPFS or the configured object-storage mirror. | Verify the metadata hash and retry after the metadata source has replicated. | | `DALP-0534` | client | 400 | no | The subscription pattern does not match any registered webhook event type or documented wildcard form. | Use an exact registered event name, a lifecycle wildcard (\*.pending, \*.provisional, \*.final, \*.retracted, *.recalled), a prefix wildcard for a registered event family (token.transfer.*), or \*. | | `DALP-0600` | domain | 409 | no | Removing a target currency would orphan its on-chain feed. Feeds can only be added. | Submit a value that is a strict superset of the existing target currencies. | | `DALP-0601` | client | 422 | no | The provider's supported-currency snapshot does not contain every requested code. | Pick currencies from the supported-currencies endpoint, or wait for the next provider refresh if you expect the code to appear. | | `DALP-0602` | dependency | 503 | yes | The addCurrencyFeeds workflow dispatch was not durably accepted. The new currencies were not persisted. | Retry the request. If it continues, contact support with the request id. | | `DALP-0603` | permission | 403 | no | Adding a target currency requires the caller's wallet to hold FEEDS\_MANAGER\_ROLE on the system AccessManager so the workflow's IssuerSignedScalarFeedFactory.createFeed call does not revert; the indexed access-control state shows the wallet is not a current member of that role. | Have a system manager grant FEEDS\_MANAGER\_ROLE to this wallet on the system, then retry. The setting is not persisted until the dispatch succeeds. | | `DALP-0604` | domain | 422 | no | The active chain has no FeedsDirectory wired up (V3-style deployment), so the workflow's IssuerSignedScalarFeedFactory.createFeed path that backs TARGET\_CURRENCIES additions cannot execute. Persisting the addition would leave the setting reflecting a currency with no path to a feed. | Use a system deployed on a chain that supports FeedsDirectory, or remove the new currency from the requested TARGET\_CURRENCIES value. | | `DALP-0605` | domain | 422 | no | Both features bind to the token transfer path and would account for the same transaction fee twice. | Remove one of the conflicting features from the template's `requiredFeatures` or `featureConfigs`. | | `DALP-0606` | client | 400 | no | The claim-yield preflight found that `quoteAccruedWad` returned zero and the holder's `consumedInterestWadExact` is positive while accrual is still open. The yield that would have been claimable was offset by interest consumed during a prior token conversion. | Wait for the next yield period to complete after the conversion. Check the conversion history to see which periods were consumed. | | `DALP-0607` | client | 400 | no | The holder's yield accrual was closed at the time of a token conversion. Once accrual closes, no further yield accumulates for this holder and past-closure periods are no longer claimable. | Yield accrual closure is permanent for this holder. No further claim is possible on this token for past-closure periods. | | `DALP-0608` | client | 400 | no | The holder has no claimable yield. Periods may already be claimed, accrual may be closed after conversion, or consumed interest may have offset the accrued amount. | Verify holder eligibility (last claimed period, conversion state) before retrying. | | `DALP-0609` | dependency | 503 | yes | Platform API could not verify or decrypt the stored KYC document envelope. | Retry later. If the document remains unavailable, contact support with the request id. | | `DALP-0610` | client | 400 | no | The uploaded KYC document payload was not valid base64 document data. | Read the document bytes, base64-encode them without data URL prefixes, and retry. | | `DALP-0611` | client | 400 | no | The declared KYC document size did not match the bytes decoded from fileData. | Send the raw file byte length in fileSize and retry the upload. | | `DALP-0612` | client | 400 | no | The KYC document MIME type did not match the file signature detected by Platform API. | Upload a JPEG, PNG, WebP, or PDF whose file extension and MIME type match the actual bytes. | | `DALP-0613` | dependency | 503 | yes | Platform API could not resolve an organization Vault EOA that can sign price-feed submissions for the organization identity. | Retry after organization deployment and indexing complete. If it continues, contact support with the request id. | | `DALP-0614` | permission | 400 | no | The requested platform setting change requires permissions to be synced before it can be persisted. | Ask an administrator to run Sync permissions for the listed participants, then retry. | | `DALP-0615` | client | 400 | no | Revealing a secret applies only to HTLC-enabled XvP settlements with external flows; the target settlement is local-only. | Skip the reveal call for local settlements, or target an HTLC settlement that has external flows. | | `DALP-0616` | client | 403 | no | The X-Executor header requested smart-wallet execution while platform Account Abstraction is disabled. | Use X-Executor: eoa or omit the header until platform Account Abstraction is enabled. | | `DALP-0617` | domain | 403 | no | The organization setting requested Account Abstraction routing while the platform-wide Account Abstraction feature is disabled. | Keep AA\_ENABLED disabled, or enable platform Account Abstraction before enabling the organization setting. | | `DALP-0618` | client | 404 | no | Every `directory.*` v2 route resolves the on-chain global Trusted Issuers Registry or Topic Scheme Registry via the per-network Directory address and the indexed `directoryInstances` table. The route returns 404 when either the Directory address is missing for the active chain or the indexed Directory has no `GLOBAL_TRUSTED_ISSUERS_REGISTRY` / `GLOBAL_TOPIC_SCHEME_REGISTRY` instance row. | Confirm the platform's Directory address is configured for the active chain and that the global registry instances have been indexed before retrying. | | `DALP-0619` | client | 404 | no | The `directory.topicSchemes.*` route looked up a topic scheme on the resolved global Topic Scheme Registry but no row matched the supplied name. The indexer reflects the on-chain registry, so a missing row means the scheme has not been registered on the global tier (or has been removed) for the active chain. | Confirm the topic scheme name (case-sensitive, no normalization) and that the indexer has caught up with the latest on-chain register/remove events before retrying. | | `DALP-0620` | client | 409 | no | Upserting a directory topic scheme is idempotent on `(name, signature)`: submitting the exact same pair returns the existing row. When the name is already registered with a different signature, the registry would silently rewrite the on-chain claim shape and break every system that inherits the scheme, so the route refuses the request before touching the chain. | Delete the existing scheme (only safe if no child registry has surfaced a stale-signature warning) or pick a new name. To change the signature in-place, call the dedicated update path once the indexed signature has been confirmed compatible. | | `DALP-0621` | client | 403 | no | The X-Executor header requested smart-wallet execution while Account Abstraction is disabled for this organization. | Ask your organization administrator to enable Account Abstraction for this organization, or omit the X-Executor header to use the organization's default routing. | | `DALP-0622` | client | 404 | no | Per-token topic-scheme writes target the token's own Topic Scheme Registry, resolved from the indexed `identityRegistries.topicSchemeRegistryAddress` column. The route returns 404 when that column is null or no `identityRegistries` row exists for the token, meaning the token inherits schemes only through the system → global chain and has nowhere to register a token-specific scheme. | Attach a token-level Topic Scheme Registry to the token before adding or removing token-specific schemes. Token-level schemes cannot be managed until the registry exists; inherited system and global schemes remain visible on the list in the meantime. | | `DALP-0623` | client | 404 | no | Removing a per-token topic scheme resolves the URL `topicId` to an indexed row on the token's own Topic Scheme Registry. The route returns 404 when the topic id matches no token-level row (it resolves to an inherited system or global scheme, to nothing in the resolved chain, or to a token-level scheme the indexer has not caught up to yet). Inherited schemes are not removable through this route. | Confirm the topic id belongs to a token-level scheme (inheritanceLevel `token`) on the resolved chain. If the scheme was just added, wait for the indexer to catch up with the on-chain register event before retrying the delete. | | `DALP-0624` | client | 404 | no | Per-token trusted-issuer writes target the token's own Trusted Issuer Registry, resolved from the indexed `identityRegistries.trustedIssuersRegistryAddress` column. The route returns 404 when that column is null or no `identityRegistries` row exists for the token, meaning the token inherits issuers only through the system → global chain and has nowhere to register a token-specific issuer. | Attach a token-level Trusted Issuer Registry to the token before adding or removing token-specific issuers. Token-level issuers cannot be managed until the registry exists; inherited system and global issuers remain visible on the list in the meantime. | | `DALP-0625` | client | 404 | no | Removing a per-token trusted issuer resolves the URL `issuerAddress` to an indexed row on the token's own Trusted Issuer Registry. The route returns 404 when the issuer address matches no token-level row (it resolves to an inherited system or global issuer, to nothing in the resolved chain, to an issuer in another token's registry, or to a token-level issuer the indexer has not caught up to yet). Inherited issuers are not removable through this route. | Confirm the issuer address belongs to a token-level issuer (inheritanceLevel `token`) on the resolved chain. If the issuer was just added, wait for the indexer to catch up with the on-chain add event before retrying the delete. | | `DALP-0626` | permission | 403 | no | The generic feeds submit route is not role-gated for price administration; price-topic submissions must flow through token set-price so the token-level admin role check applies. | Call `POST /v2/tokens/:tokenAddress/price` with a caller holding the token setPrice role. | | `DALP-0632` | client | 404 | no | The detach or rotate route resolves the live instance by typeId on the token; no `isAttached = true` row exists for that typeId. | Verify the typeId in the URL and that the feature was previously attached. Re-fetch the token's feature list and retry against an attached typeId. | | `DALP-0634` | client | 404 | no | Reading or replacing a token's compliance expression resolves the token's own identity registry from the indexed `identityRegistries` row. The route returns 404 when no `identityRegistries` row exists for the token, meaning the token has no identity registry indexed and therefore no compliance expression to read or to write. | Confirm the token has a deployed identity registry and that the indexer has caught up with its deployment. The compliance expression cannot be read or replaced until the identity registry is indexed. | | `DALP-0635` | operational | 503 | no | The chain is missing a gas-pause profile, has an undefined operations budget, or its pending base fee fell below the configured floor. | Reach out to support with the request id; this is a server-side configuration issue and is not user-correctable. | | `DALP-0636` | permission | 403 | no | The requested platform setting change needs to bind existing OnchainIDs to smart wallets, and the caller does not hold every required identity-sync role on the effective executor. | Retry as an account that holds DEFAULT\_ADMIN\_ROLE and IDENTITY\_MANAGER\_ROLE on the active system. | | `DALP-0637` | domain | 409 | no | A participant's smart wallet is already registered to a different OnchainID than the participant's EOA. | Review the participant identity binding before enabling account abstraction. | | `DALP-0638` | domain | 409 | no | An existing smart-wallet row points at a controller that does not match the participant's current signing EOA. | Repair the participant wallet pairing before enabling account abstraction. | | `DALP-0639` | client | 422 | no | The on-chain IssuerSignedScalarFeed.submit() guard ObservedAtTooFarInFuture() reverts the transaction when observedAt exceeds block.timestamp by more than the feed's driftAllowance. Accepting the request would queue a transaction that will revert and wedge the workflow. | Clamp the producer's observedAt to the latest block.timestamp for the target chain, or check the signer host's wall clock against NTP if values are minutes ahead. | | `DALP-0640` | client | 400 | no | The signed UserOperation was built with a maxPriorityFeePerGas below the organization's bundler minPriorityFee floor. | Rebuild and re-sign the UserOperation with a priority fee at or above the configured floor. | | `DALP-0645` | client | 400 | no | Token list grouping and metadata filters resolve eligible keys from `asset_type_templates.metadataSchema` visible to the caller's tenant scope. The requested key is not declared in any of those schemas, so it cannot be used as `groupBy` or as a `filter[metadata.<key>]` axis. | Verify the key name matches a field declared in a system or organization template's metadata schema. Use `data.availableKeys` (capped, alphabetically sorted) for a quick discovery list, or `meta.facets["metadata.<key>"]` on a regular list request for the authoritative bucketable axes. | | `DALP-0646` | client | 400 | no | Token list `groupBy` and facet axes are restricted to bucketable metadata field types (`string`, `enum`, `country-code`, `currency-code`, `address`). Continuous types such as `number`, `date`, `decimal-money`, `percentage`, `bps`, and `url` are filterable via `filter[metadata.<key>]` but not bucketable. | Pick a bucketable-typed key for `groupBy` and faceting, or apply this key as a filter only. | | `DALP-0647` | client | 400 | no | Identifier-typed metadata fields (`isin`, `cusip`, `lei`, `figi`) are typically unique per token. Using them as `groupBy` yields degenerate one-token-per-group results and as facet axes they yield single-bucket noise, so token list excludes them from both surfaces. | Use the identifier key as a filter via `filter[metadata.<key>]`, or pick a non-identifier bucketable-typed key for grouping and facets. | | `DALP-0648` | client | 404 | no | The active organization does not have a SPLITTER\_ADDRESS setting, so the splitter contract cannot be addressed. | Install the refund splitter through the system deployment workflow, then retry after the setting is available. | | `DALP-0649` | dependency | 503 | yes | Platform API could not resolve the indexed AA refund-loop prerequisites or read the required on-chain splitter state. | Retry after the indexer and RPC provider are healthy. If the problem continues, contact support with the request id. | | `DALP-0650` | client | 422 | no | The splitter basis-point value must fit the contract range used to split refunds between the bundler and paymaster. | Use an integer value from 0 through 10000. | | `DALP-0651` | client | 422 | no | AA runway alerting requires the critical-days threshold to fire before the warning-days threshold. | Use a positive criticalDays value that is lower than warnDays. | | `DALP-0652` | domain | 409 | no | Account abstraction is a one-way door: once enabled for an organization it can no longer be turned off. | Account abstraction must stay enabled. No action is required; leave AA enabled. | | `DALP-0653` | client | 422 | no | The `/v2/tokens/:tokenAddress/treasury/health` route resolved a feature row whose `treasury` column is the zero address. The badge cannot compose a meaningful balance, allowance, or status against the zero address, so the route refuses up front rather than surface a misleading `red` badge. | Use the bond or yield feature's Set treasury control to configure a non-zero treasury wallet, then refetch the treasury-health endpoint. | | `DALP-0654` | dependency | 502 | yes | The treasury-health badge issues exactly one live `IERC20.balanceOf(treasury)` call against the configured chain provider. That call either reverted or could not be reached, so the badge cannot render an authoritative balance and refuses to fall back to indexer state (the balance is operator-mutable and the indexer's `tokenBalances` row would be stale). | Retry once the chain provider is reachable. If the failure persists, verify the configured RPC endpoint for the active chain and the denomination asset address before retrying. | | `DALP-0655` | client | 422 | no | The `/v2/tokens/:tokenAddress/treasury/health` route composes one badge against a single treasury wallet, denomination asset, and implementation classification. When the maturity-redemption and fixed-treasury-yield features attached to the same token resolve to different values for any of those, a single-treasury badge would compare one feature's allowance against another feature's balance and report a misleading status, so the route fails closed instead. | Reconfigure the maturity-redemption and fixed-treasury-yield features so they share the same treasury wallet, denomination asset, and implementation classification, then refetch the treasury-health endpoint. | | `DALP-0656` | dependency | 503 | yes | The `/v2/tokens/:tokenAddress/treasury/health` route reads the indexed `v_bond_status` view for the authoritative `denominationRequired` ceiling driving the redemption approval. The maturity-redemption feature is attached but the view has not landed a row yet, so collapsing the missing required amount to zero would render a false `green` badge while the indexer catches up. | Retry after the indexer catches up to the latest `idxr_token_bonds` insert. If the failure persists, verify the indexer is making forward progress on the active chain. | | `DALP-0657` | client | 404 | yes | The requested atBlock value is ahead of the indexer head for the historical-balances feature; no checkpoint slice covers it yet. | Wait for the indexer to catch up to the requested block, or pick a lower block from the picker's latest-indexed default. | | `DALP-0658` | dependency | 503 | yes | The blockchain indexer is rebuilding its dataset (a zero-downtime reindex), so onboarding deploy reads would observe stale or partial state until it catches up. | Wait for the Retry-After interval, then retry the deploy. Clients that did not opt into this backpressure are unaffected. | | `DALP-0659` | auth | 403 | no | The authenticator code did not pass the identity provider's verification for this signing request. | Enter a fresh code from your authenticator app and try the operation again. | | `DALP-0660` | dependency | 503 | yes | Platform API could not reach the identity provider to complete the verification for this signing request. | Retry after a short backoff; if it persists, contact support with the request id. | | `DALP-0661` | auth | 403 | no | The requested permit owner does not match the authenticated caller's token-holding wallet, and a holder may only authorise allowances against their own balance. | Omit the owner field, or set it to your own wallet address, and sign again. | | `DALP-0662` | client | 404 | no | No DALP-stored signed permit with this id exists in the active organization scope. | Verify the signed permit id and that it belongs to your organization before retrying. | | `DALP-0663` | client | 409 | no | This signed permit was already submitted on-chain, so relaying it again would replay a consumed nonce. | Use a freshly signed permit; a relayed permit cannot be relayed twice. | | `DALP-0664` | client | 409 | no | The permit is expired (its deadline passed) or out of order: its nonce does not equal the owner's current on-chain EIP-2612 nonce, so the relay would revert. | Relay pending permits in nonce order, and sign a new permit if the deadline has passed. | | `DALP-0665` | client | 409 | yes | Two sign requests for the same holder raced to the same nonce; only one pending permit may exist per nonce. | Retry the request. A fresh nonce is assigned on the next attempt. | | `DALP-0666` | client | 400 | no | Marking the stored permit relayed must run after the relay settles on-chain. `Prefer: respond-async` (and a hybrid wait timeout) returns before settlement, so the stored permit would never flip to relayed and would later display as expired. | Retry the relay without the `Prefer: respond-async` header. | | `DALP-0667` | client | 404 | no | The requested invocation id is not present in the Workflow Engine admin inventory. | Run the doctor route to inspect current invocations and confirm the id. | | `DALP-0668` | client | 409 | no | Only paused invocations can be resumed through this route. | Inspect the invocation with the doctor route and choose recover-stuck-workflow or kill+purge if it is wedged in another state. | | `DALP-0669` | client | 400 | no | Resuming multiple paused invocations requires `confirm: true` after reviewing the dry-run preview. | Call this route with `dryRun: true` first, then retry with `confirm: true`. | | `DALP-0670` | client | 409 | no | Each platform user must have a unique email address. | Use a different email or open the existing user in User management. | | `DALP-0671` | operational | 409 | yes | Creating a user runs in two steps. The first step created the user and wallet, and the second step that registers the on-chain identity did not finish before the request ended. | Send the same create request again with the same organization and email. The platform reuses the existing user and wallet and resumes identity registration. | | `DALP-9070` | client | 400 | no | The source address does not hold enough available tokens for this transfer. | Reduce the transfer amount or mint/transfer tokens to the source address, then retry. | | `DALP-9071` | client | 400 | no | The address does not hold enough available tokens for this burn. | Reduce the burn amount or transfer tokens to the address, then retry. | | `DALP-9072` | domain | 422 | no | External token registration requires ERC-20 metadata so denomination-quoted price feeds can resolve the asset after token creation. | Register a contract that implements ERC-20 metadata, or verify the address and network before retrying. | | `DALP-9073` | domain | 422 | no | Bond and maturity assets seed a denomination-quoted price feed that reads ERC-20 metadata on-chain after deploy. | Choose a denomination asset that implements ERC-20 metadata, or register the external token with valid ERC-20 metadata before creating the bond. | | `DALP-9074` | client | 409 | no | The add-member request was rejected, the user may already belong to this organization, or the provided user id does not exist. | Verify the user id is correct and check whether the user is already a member of the organization. | | `DALP-9075` | permission | 403 | no | The active organization has not yet completed onboarding. Member management is locked until deployment is finished. | Wait for the organization to complete onboarding before adding members. | | `DALP-9076` | permission | 403 | no | Only an existing organization owner can add a new member with the owner role. | Use an account that holds the organization owner role, or add the member with the member role instead. | | `DALP-9077` | client | 409 | no | Maturity-redemption tokens stop ordinary issuance once they are matured. The redemption budget is fixed to the token supply at maturity. | Do not mint this token after maturity. Use the existing maturity treasury top-up path to fund redemptions, or issue a new instrument if new supply is required. | | `DALP-9078` | client | 403 | no | The stored secret unlocks settlement execution and the first stored value wins, so accepting a secret from any other participant would let them squat a value the creator can never overwrite. | Ask the participant who created the settlement to store the secret. | | `DALP-9079` | dependency | 503 | yes | The preflight reads symbol() and decimals() live from the chain; that RPC request failed to reach a usable response (connection error, timeout, or rate limit) rather than the contract reverting. | Retry after the Retry-After interval. If it persists, check the network's RPC endpoint health. | | `DALP-9080` | operational | 409 | yes | A full convert with closeInterestOnConversion settles convertible interest in bounded windows (104 periods each). This holder's backlog needs more windows than one request drains, or a drain batch was queued asynchronously, so the final convert was withheld to avoid an UnsettledConvertibleInterest revert. | Re-submit the same convert request. Each attempt drains further batches from the durable on-chain cursor; the conversion completes once the backlog is fully settled. | | `DALP-9082` | client | 400 | no | The requested signature deadline is at or before the current time, so `permit()` would always revert on-chain and the custodial signature could never be relayed. | Sign a new permit with a deadline in the future. | ## Surface coverage [#surface-coverage] | Surface | Transport | Coverage | Public adapter behavior | | ------------------------------------ | --------- | ----------- | ------------------------------------------------------------------------------------------------------------ | | Better Auth | hono | excluded | pass-through | | Known contract revert | orpc-rest | proof-slice | Preserve CONTRACT\_ERROR data and DALP code while adding unified registry metadata. | | Workflow Engine dependency failures | orpc-rest | proof-slice | Return retryable dependency guidance through the unified public envelope. | | Indexer database dependency failures | orpc-rest | in-scope | Report degraded indexer schema reads through registry observability while preserving safe fallback behavior. | | Bundler JSON-RPC handler | json-rpc | proof-slice | Preserve JSON-RPC 2.0 error framing and include registry data under error.data. | | oRPC RPC | orpc-rpc | proof-slice | Carry the same registry identity and public copy through the RPC-compatible error payload. | | oRPC REST | orpc-rest | proof-slice | Return the unified public error envelope for current REST failures. | | Platform API SSE streams | sse | proof-slice | Emit a protocol-valid error event after stream start or direct envelope before stream start. | | Hono unknown fallback | hono | proof-slice | Return the safe unknown public envelope after redaction and telemetry emission. |