DPE-#### — short for Data Portal Error.
The code names the condition, not the wording. Copy gets improved over time; the code does not
change with it, so it is safe to search for on this page, to bookmark, or to quote to support. The
same codes appear in Data Portal API responses, so a failure reads the same whether you hit it in
the console or from a script.
This page lists every code the product can return, what each one means, and what to do about it.
If you do not have a code in hand, start from Troubleshooting
instead, which routes by symptom.
Alongside the code, each error shows a short reference. That identifies your specific
occurrence rather than the class of problem, so include it when you contact support — it is
what lets us find the exact event in our logs.
How to read an entry
Every entry says what happened and, where you can act on it, what to do next. The category tells you whether acting is worth your time at all:
The first digit groups the code by the area it comes from:
Connections and data sources | Platform | Request validation | Ingestion and tasks | Queries | Schema and table configuration
Connections and data sources
DPE-1041 — Not enough records to sample
We read the source but found no records to sample, so the schema could not be inferred. User correctable — you can correct this. What to do- Check the path or query points at files that contain data.
- If a filter is set, confirm it is not excluding every record.
- Confirm the credentials can read the objects, not just list them.
DPE-1042 — Catalog rejected our credentials
The data catalog refused access to that location with the credentials configured for this connection. User correctable — you can correct this. What to do- Confirm the role has list and read permission for the catalog and bucket.
- Confirm the configured region matches the bucket region.
DPE-1043 — Catalog configuration incomplete
This connection is missing the catalog settings needed to browse it. User correctable — you can correct this. What to do- Provide the catalog type and its configuration on the connection, then test again.
DPE-1044 — Kafka credentials rejected
The stream refused the credentials configured for this connection. User correctable — you can correct this. What to do- Check the SASL mechanism, username and password on the connection.
- Confirm the credentials have permission to read the topic.
DPE-1045 — Could not create the stream consumer
The stream consumer could not be created with the settings on this connection. User correctable — you can correct this. What to do- Check the broker list, security protocol and topic name.
- Confirm the topic exists and is reachable from this environment.
DPE-1046 — Stream messages could not be decoded
Messages were read from the stream but could not be decoded with the configured format. User correctable — you can correct this. What to do- Confirm the message format matches what the topic actually produces.
- If a schema registry is used, confirm its URL and credentials.
DPE-1047 — Delta table could not be read
The Delta table could not be opened at the configured location. User correctable — you can correct this. What to do- Confirm the table path points at the Delta table root, not a data file.
- Confirm the credentials can read the _delta_log directory.
DPE-1048 — Preview could not read the source data
We reached the source but could not read the data needed to build a preview. User correctable — you can correct this. What to do- Confirm the file format matches the configured format.
- If the location spans regions, confirm the configured region matches the bucket.
DPE-1049 — Not authorized to preview this table
Your account is not authorized to load this table for preview. User correctable — you can correct this. What to do- Ask a workspace administrator to grant read access to this table.
DPE-1050 — No files matched the path
Nothing at the configured path matched the file pattern, so there was no data to read. User correctable — you can correct this. What to do- Check the folder path and the file pattern for a typo.
- Confirm the files are present and that this connection can list them.
DPE-1051 — The data source was busy
The data source reported that it is temporarily unavailable, so the read did not complete. Transient — temporary; retrying usually works. What to do- Wait a moment and try again.
DPE-1052 — A value was outside the allowed range
One of the values supplied for this connection was rejected by the data source as out of range. User correctable — you can correct this. What to do- Review the highlighted field and supply a value the data source accepts.
DPE-1053 — The file could not be read
The file{file} could not be read. It may be incomplete, or its format may not match what this connection expects.
User correctable — you can correct this.
What to do
- Confirm the file’s real format matches the format configured on this connection (
{format}). - Confirm the file is complete and not truncated.
- Confirm this connection has read access to that path.
DPE-1054 — No files matched that path
Nothing at{path} matched, so there was no data to read.
User correctable — you can correct this.
What to do
- Check the path and the file pattern for a typo.
- Confirm files are present at that location and this connection can list them.
DPE-1055 — Access was denied while reading this table
The credentials this data source uses were refused the{action} permission needed to read the table.
User correctable — you can correct this.
What to do
- Grant
{action}to the role or user configured on this data source. - If the permission was granted just now, the decision may still be cached — try again shortly.
DPE-1056 — The storage credentials cannot read that data
The credentials configured for this catalog’s storage were refused read access to the data file at{path}.
User correctable — you can correct this.
What to do
- Grant read access to that prefix for the identity configured under the catalog’s storage authentication settings.
- If the prefix is correct and access was granted recently, try again shortly.
DPE-1057 — The catalog would not let us sign in
The lakehouse catalog refused the sign-in for this data source’s credentials. User correctable — you can correct this. What to do- Check that the sign-in details saved on this data source are still valid and have not been revoked.
- Confirm the account they belong to is entitled to use the catalog’s REST API — some workspaces require an explicit entitlement before that API answers at all.
- Confirm the catalog URL and warehouse name are the ones intended.
Platform
DPE-0000 — Something went wrong on our side
This action did not complete because of an unexpected problem on our side. Internal — a defect on our side. What to do- Retry the action.
- If it happens again, contact StarTree support and quote the reference shown with this error.
DPE-5101 — The system is busy
We could not complete your request because the service is at capacity right now. Transient — temporary; retrying usually works. What to do- Wait a moment and try again.
DPE-5102 — The system is busy
A database operation could not complete right now. Transient — temporary; retrying usually works. What to do- Wait a moment and try again.
DPE-5103 — The system is busy
A database operation could not complete right now. Transient — temporary; retrying usually works. What to do- Wait a moment and try again.
DPE-5104 — A service we depend on is unavailable
A service this action depends on could not be reached. This is on our side, not your configuration. Upstream — a service we depend on did not answer as expected. What to do- Retry in a few minutes.
- If it persists, contact StarTree support and quote the reference shown with this error.
DPE-5105 — A service we depend on is unavailable
A service this action depends on did not respond. This is on our side, not your configuration. Upstream — a service we depend on did not answer as expected. What to do- Retry in a few minutes.
- If it persists, contact StarTree support and quote the reference shown with this error.
DPE-5106 — The cluster is not reachable
We could not reach the cluster that stores this dataset. This is on our side, not your configuration. Upstream — a service we depend on did not answer as expected. What to do- Retry in a few minutes.
- If it persists, contact StarTree support and quote the reference shown with this error.
DPE-5107 — The cluster is at capacity
The cluster declined this request because it is protecting itself from overload. Upstream — a service we depend on did not answer as expected. What to do- Retry in a few minutes.
DPE-5108 — Something went wrong on our side
The cluster returned an error we could not interpret, so the action did not complete. Internal — a defect on our side. What to do- Retry the action.
- If it happens again, contact StarTree support and quote the reference shown with this error.
DPE-5109 — The request could not be read
The request body was not valid JSON, so it could not be read and nothing was changed. User correctable — you can correct this. What to do- Reload the page and try the action again.
- If you are calling the API directly, check the body is well-formed JSON and that Content-Type is application/json.
DPE-5110 — A service we depend on is unavailable
A service this action depends on did not respond in time. This is on our side, not your configuration. Upstream — a service we depend on did not answer as expected. What to do- Retry in a few minutes.
- If it persists, contact StarTree support and quote the reference shown with this error.
DPE-5111 — That action is not available here
This request used a method this address does not accept, so nothing was changed. Internal — a defect on our side. What to do- Reload the page and try again.
- If it happens again, contact StarTree support and quote the reference shown with this error.
DPE-5112 — That address does not exist
Nothing on this service answers that address, so the request was not processed. Internal — a defect on our side. What to do- Reload the page and try again.
- If it happens again, contact StarTree support and quote the reference shown with this error.
DPE-5117 — A stored setting could not be read
One of this connection’s saved settings is incomplete, so it could not be loaded. Internal — a defect on our side. What to do- Reopen the connection and save it again to rewrite the stored settings.
- If that does not help, contact StarTree support and quote the reference shown with this error.
DPE-5118 — The request was cancelled
The request ended before a reply could be sent, usually because the page was closed or navigated away from. Informational — not a failure; act only if you want a different outcome.DPE-5119 — Cluster health is not available right now
The cluster answered the health request without any detail, so there is nothing to show yet. Upstream — a service we depend on did not answer as expected. What to do- Try again in a few moments.
- If it stays empty, contact StarTree support and quote the reference shown with this message.
DPE-5120 — Something went wrong on our side
This action did not complete because a database request could not be carried out. Internal — a defect on our side. What to do- Retry the action.
- If it happens again, contact StarTree support and quote the reference shown with this message.
Request validation
DPE-5201 — Ingestion type not recognised
This dataset is configured with an ingestion type this version does not recognise. User correctable — you can correct this. What to do- Reopen the dataset and select an ingestion type from the list.
- If the problem persists, contact StarTree support and quote the reference shown with this error.
DPE-5202 — A required value was missing
The request did not include{param}, which is required to complete it.
User correctable — you can correct this.
What to do
- Reload the page and try the action again.
- If you are calling the API directly, include
{param}in the request.
DPE-5203 — You do not have access to this
Your account is not authorized for this action in this workspace. Informational — not a failure; act only if you want a different outcome. What to do- Ask a workspace administrator to grant the permission you need.
DPE-5204 — You do not have access to this
Your account is not authorized for this action in the cluster. Informational — not a failure; act only if you want a different outcome. What to do- Ask a workspace administrator to grant the permission you need.
DPE-5205 — You do not have access to this
Your account is not authorized for this action in this workspace. Informational — not a failure; act only if you want a different outcome. What to do- Ask a workspace administrator to grant the permission you need.
DPE-5206 — Connection not found
The connection this dataset uses is no longer available. User correctable — you can correct this. What to do- Reselect a connection for this dataset, or recreate the connection.
DPE-5207 — Uploaded file could not be read
The uploaded file could not be read. It may have been interrupted, or exceed the size limit. User correctable — you can correct this. What to do- Upload the file again.
- If the file is large, upload it to object storage and connect to it instead.
DPE-5208 — Uploaded file was empty
The uploaded file contained no records, so no schema could be inferred. User correctable — you can correct this. What to do- Upload a file that contains at least one record.
DPE-5209 — Setting not recognised
One of the settings sent with this request is not recognised. User correctable — you can correct this. What to do- Reload the page and try again so the latest options are used.
DPE-5210 — That dataset could not be found
The dataset{srn} no longer exists, or it was renamed while this page was open.
User correctable — you can correct this.
What to do
- Refresh the page and open the dataset from the list again.
DPE-5211 — You do not have access to that
Your account does not have permission to{action}.
User correctable — you can correct this.
What to do
- Ask a workspace administrator to grant the permission you need.
DPE-5212 — That value is not valid here
The value supplied for{param} is not one this request accepts.
User correctable — you can correct this.
What to do
- Go back and open the item from the list rather than editing the address bar.
- If you are calling the API directly, check the type
{param}expects.
DPE-5213 — A required value was not supplied
{field} is required, and the request did not include it.
User correctable — you can correct this.
What to do
- Fill in
{field}and try again.
DPE-5214 — A required value was not supplied
The request was missing a value it needs, so it was not processed. User correctable — you can correct this. What to do- Reload the page and try the action again.
- If you are calling the API directly, check the request against the API reference.
DPE-5215 — Choose a source type
This request did not say which kind of source it is for. User correctable — you can correct this. What to do- Pick a source type and try again. Accepted values:
{types}.
DPE-5216 — That name is already taken
Another data source in this workspace already uses this name. User correctable — you can correct this. What to do- Choose a different name, or edit the existing data source of that name instead.
DPE-5217 — That dataset belongs to a different workspace
The dataset named in the request is not in the workspace the request was made against. User correctable — you can correct this. What to do- Switch to the workspace that owns the dataset, then try again.
- If you reached this from a saved link, the link may point at another workspace.
DPE-5218 — That value is not one of the accepted options
{parameter} only accepts a fixed set of values, and the one supplied is not among them.
User correctable — you can correct this.
What to do
- Choose one of the offered values for
{parameter}.
DPE-5219 — That data source type is not available here
That data source type is not one this environment can use. User correctable — you can correct this. What to do- Choose one of the data source types offered when creating a data source.
- If you expect this type to be available, contact StarTree support and quote the reference shown with this message.
Ingestion and tasks
DPE-3104 — No ingestion runs yet
This dataset has no ingestion task scheduled, so there is no run history to show. Informational — not a failure; act only if you want a different outcome. What to do- Schedule an ingestion task to get started.
DPE-3105 — No ingestion runs yet
No ingestion run has been recorded for this dataset yet, so there is no progress to report. Informational — not a failure; act only if you want a different outcome. What to do- Schedule an ingestion task, then check back once the first run starts.
DPE-3106 — No files matched this run
The ingestion task ran but found no new input files matching the configured path, so nothing was scheduled. Informational — not a failure; act only if you want a different outcome. What to do- Confirm the input path and file pattern point at the files you expect.
- If files were already ingested, this is expected — each file is processed once.
DPE-3107 — Ingestion service unavailable
We could not reach the service that reports ingestion progress. This is on our side, not your configuration. Upstream — a service we depend on did not answer as expected. What to do- Retry in a few minutes.
- If it persists, contact StarTree support and quote the reference shown with this error.
DPE-3108 — Ingestion task type not supported
The task type requested for this dataset is not one this cluster can run. User correctable — you can correct this. What to do- Choose a task type from the supported list for your datasource.
DPE-3109 — Task configuration missing
This dataset has no configuration for the requested ingestion task, so it cannot be scheduled. User correctable — you can correct this. What to do- Add the task configuration to the dataset, then schedule the task again.
DPE-3110 — Ingestion task scheduling failed
The scheduler rejected the request to run this ingestion task. This is on our side, not your configuration. Upstream — a service we depend on did not answer as expected. What to do- Retry shortly.
- If it persists, contact StarTree support and quote the reference shown with this error.
DPE-3111 — Ingestion state unavailable
Ingestion is not running for this dataset, and we could not tell whether it was never started or the cluster is missing state for it. Upstream — a service we depend on did not answer as expected. What to do- Refresh in a moment to see whether it recovers.
- If it persists, contact StarTree support and quote the reference shown with this error.
DPE-3112 — Could not read ingestion progress
We could not read the consuming-segment information for this dataset. This is on our side. Upstream — a service we depend on did not answer as expected. What to do- Retry shortly.
- If it persists, contact StarTree support and quote the reference shown with this error.
DPE-3113 — Could not reach the ingestion service
We could not reach the service that reports task progress, so its status is unavailable right now. Upstream — a service we depend on did not answer as expected. What to do- Wait a moment and refresh.
- If it keeps happening, contact StarTree support and quote the reference shown with this error.
DPE-3115 — No files found at the source path
Nothing could be listed at{uri}, so there was nothing to ingest.
User correctable — you can correct this.
What to do
- Check the path is correct and that files exist under it.
- Confirm the connection’s credentials allow listing that location.
DPE-3116 — Ingestion could not be scheduled
The ingestion run for{table} could not be scheduled.
Upstream — a service we depend on did not answer as expected.
What to do
- Try again in a moment.
- If it persists, contact StarTree support and quote the reference shown with this error.
DPE-3117 — Ingestion status is unavailable
The ingestion service did not return the task details for this dataset, so its status cannot be shown right now. Upstream — a service we depend on did not answer as expected. What to do- Wait a moment and refresh.
- If it keeps happening, contact StarTree support and quote the reference shown with this error.
DPE-3118 — Ingestion run failed
The most recent ingestion run for this dataset did not complete. Upstream — a service we depend on did not answer as expected. What to do- Open the dataset’s Tasks tab to see which run failed and what it reported.
- If runs keep failing, contact StarTree support and quote the reference shown with this error.
DPE-3119 — You do not have access to task details
Reading task details for this dataset requires a permission this account does not have. Informational — not a failure; act only if you want a different outcome.Queries
DPE-4301 — Query could not be parsed
The query could not be parsed, so it was not run. User correctable — you can correct this. What to do- Check the query for a missing keyword, quote or bracket.
DPE-4302 — Query took too long
The query did not finish within the time allowed and was stopped. Transient — temporary; retrying usually works. What to do- Narrow the time range or add a filter, then run it again.
DPE-4303 — Table not found for this query
The query references a table that does not exist in this workspace. Informational — not a failure; act only if you want a different outcome. What to do- Check the table name in the query.
Schema and table configuration
DPE-2201 — Dataset name not allowed
Dataset names may use lowercase letters, numbers, hyphens and underscores only. User correctable — you can correct this. What to do- Rename the dataset using lowercase letters, numbers, hyphens or underscores.
DPE-2202 — Dataset name is required
A dataset name was not provided, so the dataset could not be created. User correctable — you can correct this. What to do- Enter a dataset name and try again.
DPE-2203 — Double underscore not allowed in name
Dataset names cannot contain a double underscore, which Pinot reserves for internal naming. User correctable — you can correct this. What to do- Remove the double underscore from the dataset name.
DPE-2204 — Column name not allowed
One or more column names use characters that cannot be indexed. User correctable — you can correct this. What to do- Rename the column to use letters, numbers and underscores only, with no spaces.
DPE-2205 — Schema is not backward-compatible
The updated schema cannot replace the existing one because it drops or changes columns already in use. User correctable — you can correct this. What to do- Keep every column from the existing schema in the new one.
- To change a column type, create a new dataset instead of editing this one.
DPE-2206 — Table configuration rejected
Pinot rejected the table configuration for this dataset. User correctable — you can correct this. What to do- Review the highlighted settings and try again.
DPE-2207 — Datetime format not recognised
The datetime format configured for a column does not match the values in the source data. User correctable — you can correct this. What to do- Correct the datetime format so it matches the source values.
DPE-2208 — This dataset already exists
A dataset with this name already exists in the workspace. User correctable — you can correct this. What to do- Choose a different name, or open the existing dataset.
DPE-2209 — Dataset not found
This dataset is no longer available. It may have been deleted, or the link may be out of date. Informational — not a failure; act only if you want a different outcome. What to do- Refresh the page, then open the dataset from the list.
DPE-2210 — Dataset not found
This dataset is no longer available. It may have been deleted, or the link may be out of date. Informational — not a failure; act only if you want a different outcome. What to do- Refresh the page, then open the dataset from the list.
DPE-2211 — Transform refers to a field that does not exist
The transform for column{columnName} refers to {property}, which is not present on the source record.
User correctable — you can correct this.
What to do
- Check the field name against your source schema.
- If the field is optional, guard the transform so it tolerates a missing value.
DPE-2212 — Transform expression could not be evaluated
A transform or filter expression on this dataset could not be evaluated against the source data. User correctable — you can correct this. What to do- Review the expression for the affected column.
- Confirm every field the expression references exists in the source.
DPE-2213 — Column value did not match its type
A value in column{columnName} could not be converted to the type configured for it.
User correctable — you can correct this.
What to do
- Correct the column type to match the source values, or fix the source data.
DPE-2214 — Dataset not found in Pinot
This dataset does not exist in the cluster. It may have been deleted, or never finished creating. Informational — not a failure; act only if you want a different outcome. What to do- Refresh the page, then open the dataset from the list.
DPE-2215 — That identifier is not valid
One of the identifiers in this request is not in a form this service recognises. User correctable — you can correct this. What to do- Reload the page and try the action again.
- If you are calling the API directly, check the identifier you sent.
DPE-2216 — Dataset removed
The dataset{table} was removed. Its entry here will clear on its own shortly.
Informational — not a failure; act only if you want a different outcome.
What to do
- Refresh the list in a moment.
DPE-2217 — Dimension table needs a primary key
A dimension table has to declare at least one primary key column, and this one declares none. User correctable — you can correct this. What to do- Add one or more columns to primaryKeyColumns in the schema.
- If this is not meant to be a dimension table, clear isDimTable in the table configuration.
DPE-2218 — That server tenant does not exist
The server tenant named in this table configuration has no instances, so the table cannot be placed. User correctable — you can correct this. What to do- Check the server tenant name in the table configuration against the tenants that exist.
- If the tenant is correct, confirm it has server instances assigned.
DPE-2219 — A dataset of that name already exists
{table} already exists, so it cannot be created again.
User correctable — you can correct this.
What to do
- Choose a different name for the new dataset.
- To change the existing one, open it and edit its configuration instead of creating it again.
DPE-2220 — That setting cannot be changed after creation
{fields} cannot be changed on an existing dataset, because doing so would make the data already stored inconsistent with the new setting.
User correctable — you can correct this.
What to do
- Revert those fields to their current values to save the rest of your changes.
- To adopt the new setting, create a new dataset with it and move the data over.
DPE-2221 — A value in the configuration has the wrong type
The value{value} was given where a {targetType} is required, so the configuration could not be read.
User correctable — you can correct this.
What to do
- Replace
{value}with a valid{targetType}. - If the value stands for missing data, leave the field out rather than filling it with a placeholder.
DPE-2222 — The configuration could not be read
Part of the dataset configuration is not valid, so it could not be applied. User correctable — you can correct this. What to do- Review the schema and table configuration for a missing or misspelled field.
- If you pasted the configuration in, check it is complete and well formed.
DPE-2223 — A timestamp did not match its declared format
The value{value} could not be read as a time using the format declared for that column.
User correctable — you can correct this.
What to do
- Correct the time format on the column so it describes the values actually present.
- If the values are in a different unit than declared, set the matching unit.