# DALP-0700 to DALP-0799

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

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

| DALP Code | Machine name | Category | Message | Why | Suggested Fix | Severity | Retryable | HTTP Status |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| DALP-0705 | `DEBUG_BUNDLE_WINDOW_INVALID` | client | The debug bundle time window was not accepted. | The debug bundle window starts at or after its end. | Send a start before the end, or leave both out to export the default window. | info | No | 400 |
| DALP-0706 | `TOKEN_NOT_FOUND` | domain | Token not found. | The token is not present in the serving projection. | Confirm the token reference and wait for indexing if it was created recently. | info | No | 404 |
| DALP-0707 | `ASSET_REF_INVALID` | client | Token reference is incomplete. | The asset reference cannot identify a token in its stated family. | Send an EVM contract address, or a Canton instrument id together with its instrument admin. | info | No | 400 |
| DALP-0708 | `TOKEN_CROSS_FAMILY_MISMATCH` | client | Values from two chain families were combined. | The request combines values that belong to different chain families. | Filter and address the token within one family. | info | No | 400 |
| DALP-0709 | `TOKEN_PAUSED` | domain | The token is paused. | The token is paused, and this operation changes balances. | Unpause the token, then run the operation again. | info | No | 409 |
| DALP-0711 | `TOKEN_MUTATION_REJECTED` | domain | The token's state does not allow this write. | The token's current state does not allow this write. | Read the token, resolve the named condition, and write again. | info | No | 409 |
| DALP-0712 | `TOKEN_ROLE_REQUIREMENT_NOT_MET` | permission | This operation is not available to the caller. | The acting wallet holds none of the roles this operation requires. | Ask an administrator to grant one of the listed roles on this token. | info | No | 403 |
| DALP-0713 | `TOKEN_DOCUMENT_INVALID` | client | Document upload does not match its declaration. | The uploaded document does not match what the request declared. | Upload the file again and confirm it with its real size and type. | info | No | 422 |
| DALP-0715 | `TOKEN_COMPLIANCE_REJECTED` | permission | A compliance rule refused the transfer. | A compliance rule on this token refused the transfer. | Clear the named compliance blocker, then transfer again. | info | No | 403 |
| DALP-0717 | `TOKEN_DEPENDENCY_UNAVAILABLE` | dependency | A dependency of this route is unavailable. | A dependency this route needs did not answer. | Retry; the request was not applied. | error | Yes | 503 |
| DALP-0718 | `OBLIGATION_IMMUTABLE` | domain | This obligation cannot be edited. | The obligation is a platform catalogue entry, the same in every deployment, so no organisation can change it or add filing periods to it. | Copy the catalogue obligation and change the copy. | info | No | 409 |
| DALP-0719 | `APPROVER_SHORTFALL` | client | The organization has too few approvers to publish. | The organization has fewer approvers than maker-checker publishing requires. | Give the organization a second owner, then publish again. | info | No | 422 |
| DALP-0720 | `OBLIGATION_INVALID` | client | The obligation configuration does not hold together. | The obligation configuration is internally inconsistent. `data.violations` lists every problem the platform found, so they can be corrected in one pass. | Correct every violation listed in `data.violations`, then send the request again. | info | No | 422 |
| DALP-0721 | `TRANSITION_REFUSED` | domain | The submission's state does not allow this act. | The filing lifecycle does not permit this act from the submission's or filing period's current state. `data.from` and `data.event` name both. | Read the submission again and choose an act its current state permits. | info | No | 409 |
| DALP-0722 | `REPORTING_FILING_ROW_VERSION_CONFLICT` | domain | The submission changed before this act was applied. | Someone else changed this filing after you opened it, so your action was not applied. | Reload the filing, check its current state, and try the action again. | info | No | 409 |
| DALP-0723 | `SIGN_OFF_REFUSED` | domain | Sign-off was refused. | The artifact changed after the approver reviewed it, so the approved digest no longer matches. `data.reason` is `digest-moved`. | Review the current artifact, then approve the digest of the version you read. | info | No | 409 |
| DALP-0724 | `REACH_BACK_EXCEEDED` | permission | The filing period is outside the reach-back window. | The filing period is older than the reach-back window its obligation allows. | Raise the obligation's reach-back window before filing against a period this old. | info | No | 409 |
| DALP-0725 | `REPORTING_GENERATION_CONFLICT` | domain | Another report generation holds this slot. | Another generation holds this organisation's slot, so no run was started for this filing. | Start the generation again once the running one finishes. | info | Yes | 409 |
| DALP-0726 | `REPORTING_COVERAGE_UNAVAILABLE` | domain | The period starts before the platform's recorded history. | The reference period begins before the earliest date the platform has recorded history for. | File this period outside the platform; it predates the named date. | info | No | 422 |
| DALP-0727 | `ANCHOR_ENABLEMENT_REFUSED` | domain | The anchoring change was refused. | A check refused turning anchoring on or off for this obligation, or accepting a missing anchor. `data.reason` names which check. | Read `data.reason`. For `disclosure-not-confirmed`, confirm the disclosure with a written reason. For `no-published-version`, publish a version of the obligation. For `blocking-severity-unavailable`, choose a warning severity where publication is the fulfilment act. For `issuer-untrusted` or `issuer-unresolved`, register the issuer as trusted for the document-hash topic. For `already-disabled`, `no-standing-exception` or `already-overridden`, send no further request. | info | No | 409 |
| DALP-0728 | `OBLIGATION_NOT_FOUND` | domain | The reporting record was not found. | No reporting record of the requested kind with that identifier is visible to the caller in the active organization. A record another organization or another investor holds answers the same way, so the reply never confirms that an identifier exists elsewhere. | List the records of that kind, such as obligations, statements, or confirmations, and use an identifier from that list. | info | No | 404 |
| DALP-0730 | `EXTERNAL_TOKEN_ALREADY_REGISTERED` | domain | This token is already registered. | The token address is already registered as an external token for this organization. | Open the existing registration instead of registering the address a second time. | info | No | 422 |
| DALP-0732 | `RETURNS_SNAPSHOT_CONTENTION` | dependency | The returns snapshot could not be taken. | The snapshot reads every position in one transaction and lost that read to concurrent writers twice, so it stopped rather than answer a torn total. | Retry after a short backoff. | error | Yes | 503 |
| DALP-0733 | `PORTFOLIO_RESOURCE_NOT_FOUND` | client | Portfolio resource was not found. | The requested portfolio resource does not exist in the active organization. | Verify the identifier and the active organization, then request it again. | info | No | 404 |
| DALP-0734 | `GOVERNANCE_BALLOT_REJECTED` | client | The ballot wasn't accepted. | The ballot did not satisfy one of the rules a cast has to pass. The `reason` field names which one. | Read `reason`, correct that one condition, and send the ballot again. | info | No | 422 |
| DALP-0735 | `GOVERNANCE_STATE_UNAVAILABLE` | dependency | Governance state is temporarily unavailable. | Governance state could not be read from the chain or from its indexed projection. | Retry after a short backoff. If the problem continues, contact support with the request id. | error | Yes | 503 |
| DALP-0736 | `EXTERNAL_TOKEN_REGISTRATION_REJECTED` | client | The external token wasn't registered. | The address did not pass on-chain ERC-20 metadata verification, or it is already registered. | Check that the address exposes name, symbol, and decimals on this chain, and that it is not registered already. | info | No | 422 |
| DALP-0737 | `PORTFOLIO_RETURNS_UNAVAILABLE` | dependency | Portfolio returns are temporarily unavailable. | A return amount has incomplete denomination metadata, its denomination asset has no price, or no configured FX path connects its price currency to the organization's base currency. The response data names the currencies and reason. | For `denomination-metadata-missing`, wait for the denomination token to index. For `denomination-unpriced`, publish a price for the denomination asset. For `fx-path-unavailable`, configure a feed path from `priceCurrency` to `baseCurrency`, then retry after pricing updates. | error | Yes | 503 |
| DALP-0738 | `ARTIFACT_UNAVAILABLE` | domain | This filing has no stored artifact. | No artifact was ever stored for this submission, so there is nothing to download and nothing was erased. A split artifact is served as its parts, an erased one answers with its tombstone, and one under legal hold stays retrievable; none of those reaches this error. | Read the submission's state. An artifact exists only once generation has written one, so wait for the filing to be generated or read a submission that already has been. | info | No | 409 |
| DALP-0744 | `FILING_NOT_FOUND` | domain | The filing period or submission was not found. | No filing period or submission with that identifier is visible to the active organization. `data.subject` names which of the two was addressed. A row another tenant owns answers the same way, so the reply never confirms that an identifier exists elsewhere. | List the organization's filing periods and submissions, and use an identifier from that list. | info | No | 404 |
| DALP-0746 | `ANCHOR_LOOKUP_REFUSED` | client | The anchor question cannot be answered as asked. | An anchor lookup takes exactly one of a document digest, a subject identity or a registry address, and a verification takes the artifact's parts in order within the published ceilings. A page cursor the platform did not issue is refused the same way. `data.reason` names which of those the request broke. | Read `data.reason`. Send one of `digest`, `subject` or `registry` to read registry entries, or send each part's SHA-256 and byte length in the order of delivery, with `issuer`, to check a document you hold. | info | No | 422 |
| DALP-0747 | `ANCHOR_RETRY_REFUSED` | domain | This filing cannot be anchored yet. | An anchor may only fire from a discharged filing, and this submission has not been acknowledged or published. Before that the artifact can still legitimately be regenerated, and a commitment to a digest that may still change is one a document holder would later fail to reproduce, with no way to tell an honest regeneration from tampering. | Discharge the filing first: enter the authority's acknowledgement, or publish it to holders. Anchoring runs on its own at that act, and the retry route exists for the attempt that failed there. | info | No | 409 |
| DALP-0749 | `ANCHOR_WRITE_REFUSED` | domain | This document cannot be anchored. | Writing a registry entry is a permanent, public disclosure that can never be corrected, only superseded by a further entry, so every prerequisite is checked before anything reaches a chain. `data.reason` names which one refused: the confirmation of permanence was missing, the session is an operator acting as somebody else, the subject is not a usable identity, this organisation has no active system on the chosen chain, its issuer identity is inactive or has no resolvable claim key, that identity is not trusted for the document-hash topic in its own system's registry, the system carries no anchor registry, or the label would carry something identifying onto a public chain. | Read `data.reason`. Anchor as the organisation's owner or a platform administrator on your own session. Use a chain where your organisation runs a system whose anchor-registry migration has completed. Send a subject identity your issuer is trusted for, a short non-identifying label, and `disclosureConfirmed` set to true. A chain that was reached and declined is not this error: that arrives as `data.outcome` in a successful response. | info | No | 409 |
| DALP-0751 | `EXTERNAL_TOKEN_MANAGER_REQUIRED` | permission | Only a token manager can dismiss an external token. | Dismissing an external token hides it from the organization's holdings, portfolio, holder lists, token catalog, token details, and marks, and stops the platform from registering it again. It requires the tokenManager role on the organization's system. | Ask a system administrator to grant you the tokenManager role, then retry. | info | No | 403 |
| DALP-0752 | `SHAREHOLDER_LIST_NOT_FOUND` | domain | The security of this shareholder list was not found. | No security with that contract address is indexed in the active organization's system at `data.recordBlock`. A security another organization issued answers the same way, so the reply never confirms that a contract address exists elsewhere. | Use the contract address of a security the organization issued, as shown in the Console. For a security created after `data.recordBlock`, choose a later record block, or leave the block out to use the newest final block. | info | No | 404 |
| DALP-0753 | `SHAREHOLDER_LIST_REFUSED` | domain | No shareholder list can be read at this block. | The security's balance history does not reach the record block, or the record block is not final yet. `data.reason` names which, and `data.boundaryBlock` is the block the history starts at, the block the feature was detached at, or the newest final block. | For `feature-not-attached`, the security never had a historical-balances feature, so it has no record block to list. For `feature-detached`, the feature was detached at `data.boundaryBlock`: choose a record block before that block. For `enablement-after-record-block`, choose a record block at or after `data.boundaryBlock`. For `history-incomplete`, no record block can be listed, because the security had supply before the feature was attached; `data.boundaryBlock` is the block the feature was attached at. For `record-block-not-final`, wait until that block is final, or leave the block out to use the newest final block. | info | No | 422 |
| DALP-0754 | `STATEMENT_RANGE_REFUSED` | domain | No statement can be produced for this range yet. | A statement covers only blocks that are final on the chain, and the chain has not finalized the block at the end of the requested range yet. `data.periodEnd` is the inclusive end of the range the request asked for. | Choose an `end` before the newest final block, or send the same request again after the chain finalizes the block at `data.periodEnd`. | info | Yes | 422 |
| DALP-0755 | `ASSISTANT_VIEW_NOT_FOUND` | client | Saved view not found. | No saved view with that identifier was saved by the caller in the active organization. A view another member saved answers the same way to a rename, share or removal, so the reply never confirms that it exists. | List the saved views and use the identifier of a view the caller saved. | info | No | 404 |

The previous page is [DALP-0600 to DALP-0699](https://docs.settlemint.com/docs/api-reference/errors/platform-api-error-reference/dalp-0600-0699). The next page is [DALP-9000 to DALP-9099](https://docs.settlemint.com/docs/api-reference/errors/platform-api-error-reference/dalp-9000-9099).