# DALP-9200 to DALP-9299

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

This page lists the 22 errors the Platform API can return with a code from DALP-9200 to DALP-9299. 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-9243 | `TOKEN_CREATE_INPUT_ENCODING_INVALID` | client | The token creation values cannot be processed. | The token creation input cannot be represented by the durable workflow schema. | Read the message for the field or rule the request broke, correct it, then send the request again. | info | No | 422 |
| DALP-9244 | `TENANT_WALLET_RESOLUTION_FAILED` | dependency | The tenant wallet could not be resolved. | The request could not resolve the tenant wallet required for this operation. | Verify the participant wallet assignment and wallet service availability, then retry. | error | Yes | 503 |
| DALP-9252 | `USER_ASSETS_METADATA_KEY_INVALID` | client | The metadata key cannot be used for this asset query. | The requested metadata key is unknown or is not eligible for the selected filter or grouping operation. | Use one of the available metadata keys that supports this query operation. | info | No | 422 |
| DALP-9253 | `SYSTEM_READ_FAILED` | dependency | The system projection is temporarily unavailable. | The indexed system projection could not be resolved for this request. | Retry after the indexer catches up or verify the organization system setting. | error | Yes | 503 |
| DALP-9259 | `TOKEN_READ_DEPENDENCY_FAILED` | dependency | Token data is temporarily unavailable. | The indexed token projection could not be read for this request. | Retry after the indexer database is available; if the failure persists, inspect its query health. | error | Yes | 503 |
| DALP-9260 | `PORTFOLIO_PERSISTENCE_FAILED` | dependency | Portfolio data is temporarily unavailable. | The indexed portfolio data required by this endpoint could not be read or persisted. | Retry after a short backoff. If the failure continues, ask an operator to check the indexer database. | error | Yes | 503 |
| DALP-9266 | `TOKEN_FEATURE_PERSISTENCE_FAILED` | dependency | Token feature data is temporarily unavailable. | The token-feature data required by this endpoint could not be read or persisted. | Retry after a short wait. If the failure persists, check the token database, the indexer and the chain RPC. | error | Yes | 503 |
| DALP-9267 | `TOKEN_WRITE_PERSISTENCE_FAILED` | dependency | The token write could not be persisted. | A persistence operation required by the token mutation failed. | Retry after a short wait. If the failure persists, check the token database, the indexer and the chain RPC. | error | Yes | 503 |
| DALP-9269 | `COLLECTION_SORT_FIELD_UNKNOWN` | client | The sort field is not supported on this list. | List endpoints accept only the sortable fields declared for that collection. An unknown or non-sortable field name cannot order the page. | Use one of the sortable fields documented for this list endpoint, or omit `sort` to keep the default order. | info | No | 400 |
| DALP-9270 | `COLLECTION_SORT_MULTI_FIELD_UNSUPPORTED` | client | List endpoints accept a single sort field. | The collection query codec supports one sort field per request. Comma-separated multi-field sort is not implemented on the shared list infrastructure. | Send a single field in `sort` (prefix with `-` for descending) and retry. | info | No | 400 |
| DALP-9271 | `COLLECTION_FILTER_FIELD_UNKNOWN` | client | The filter field is not supported on this list. | List endpoints accept only the filterable fields declared for that collection. An unknown or non-filterable field name cannot narrow the page. | Use one of the filterable fields documented for this list endpoint, or remove the unknown filter key. | info | No | 400 |
| DALP-9272 | `COLLECTION_FILTER_OPERATOR_UNKNOWN` | client | The filter operator is not supported. | Each collection filter accepts only the operators defined for that field. An unknown operator cannot be applied safely to the list query. | Use a documented operator for the field (for example `eq`, `iLike`, `inArray`, or `between`) and retry. | info | No | 400 |
| DALP-9273 | `COLLECTION_FILTER_IN_LIST_TOO_LARGE` | client | The membership filter list is too large. | Membership filters (`inArray` and `notInArray`) cap the number of values so SQL `IN` clauses stay bounded and predictable. | Send at most 100 values in the membership list, or split the request across multiple pages or batches. | info | No | 400 |
| DALP-9274 | `COLLECTION_PAGE_LIMIT_OUT_OF_RANGE` | client | The page limit is out of range. | Every collection list bounds page size to an integer between 1 and 200 so a single request cannot pull an unbounded result set. | Set `page[limit]` to an integer from 1 through 200 and use pagination links for additional rows. | info | No | 400 |
| DALP-9275 | `COLLECTION_PAGE_OFFSET_OUT_OF_RANGE` | client | The page offset is out of range. | Collection list offsets must be integers of zero or greater. A negative offset is not a valid start position for a page. | Set `page[offset]` to an integer greater than or equal to 0. | info | No | 400 |
| DALP-9281 | `ORGANIZATION_NOT_FOUND` | client | Organization not found. | The caller is not a member of this organisation and holds no open invitation to it. | Read the organisations this account belongs to or is invited to, then send one of those ids. | info | No | 404 |
| DALP-9288 | `TOKEN_LIST_FACTORY_REGISTRY_UNAVAILABLE` | dependency | Token factory registry is not ready for this system. | The active system has no indexed token-factory registry address, so the token list cannot authorize which factories belong to the system. | Wait for the system token-factory registry to index, then retry the request. | error | Yes | 503 |
| DALP-9289 | `TOKEN_LIST_FILTER_INVALID` | client | Token list request names a sort term or field selection it does not support. | The token list orders only on its published columns and accepts one `sort` term per request, so a term that names no published column, or a comma-separated list of terms, cannot be answered, and ordering by something else would publish a page that was not asked for. The same refusal answers a `fields[token]` selection that names a member the list does not publish, and a sort on a column some holdings do not have. `data.filterId` carries the refused term as it was sent. | Send one `sort` term that names a published column (prefix it with `-` for descending order), or omit `sort` to take the default order. Select only members the list publishes in `fields[token]`. | info | No | 400 |
| DALP-9290 | `TOKEN_CREATE_AMBIGUOUS_INTEREST_PROVIDER` | domain | The conversion feature cannot resolve a usable interest provider. | The conversion feature discovers its interest provider through ERC-165. With both yield features attached it finds two, refuses to auto-select, and every interest-bearing conversion path fails closed after deployment. An explicit provider replaces that discovery, so it must itself be a deployed contract that answers ERC-165 for IConversionInterestProvider and reports the same denomination asset as the conversion. The conversion config is immutable and has no provider setter, so neither case is repairable after creation. | Set `featureConfigs.conversion.interestProvider` to a deployed interest provider that uses the conversion's denomination asset, or attach only one yield feature and leave the provider unset so discovery resolves it. | info | No | 422 |
| DALP-9291 | `TOKEN_CREATE_MARKCONVERTED_YIELD_INCOMPATIBLE` | domain | The MarkConverted debt method cannot be combined with a yield feature. | MarkConverted records a conversion without moving tokens, so it suits instruments whose token is a receipt and whose principal is held in a separate ledger. Yield features pay out on the token balance, which on such an instrument is not the amount owed. After a conversion it no longer reflects active principal either. | Pick the Burn or Lock debt method, which retire the converted principal and keep the balance accurate, or remove the yield feature from the design. | info | No | 422 |
| DALP-9298 | `TRADING_VENUE_MARKET_NOT_FOUND` | client | The instrument was not found. | The id in the request names no venue, instrument or other venue record that this caller can see in the active organisation. A venue record is an approval, trade, bust, parked fill, price alert, watchlist, access profile or calendar. | Use an instrument id from the instruments list of your organization. | info | No | 404 |
| DALP-9299 | `TRADING_VENUE_ORDER_NOT_FOUND` | client | The order was not found. | The order id does not name an order placed by a wallet the selected participant controls, the order is no longer open to cancel, or no open order matches a mass-cancel filter. | Use an order id from the working-orders list of the selected participant. | info | No | 404 |

The previous page is [DALP-9100 to DALP-9199](https://docs.settlemint.com/docs/api-reference/errors/platform-api-error-reference/dalp-9100-9199). The next page is [DALP-9300 to DALP-9399](https://docs.settlemint.com/docs/api-reference/errors/platform-api-error-reference/dalp-9300-9399).