Troubleshooting

This page lists the messages you can see while you work in the Warehouse, what each one means and what to do about it. Find the message in the table for your area, then follow the advice in the same row.

Access and popups

You see	What it means and what to do
Access denied. Required permission(s): followed by permission names	Your role does not include the permission the message names. Ask an administrator to grant it. Creating, changing and deploying need Add/Modify Warehouse Objects, and testing or running a transformation needs Execute/Abort Warehouse Objects. See Warehouse permissions and row-level security.
Access denied. You do not have permission to followed by an action	Your role cannot perform that action on this kind of table. For a Warehouse table, changes need Add/Modify Warehouse Objects and deleting needs Remove Warehouse Objects. Ask an administrator to grant the permission.
Warehouse pop-up limit reached, then You have 20 Warehouse pop-ups open or minimized. Close some before opening a new one.	You already have 20 Warehouse popups open or minimised, and minimised popups count. Close some from Open Popups in the sidebar before you open another. Each area, such as Lake, has its own limit.
Close Popup, then You have unsaved changes. Do you want to close the popup?	You are closing an editor with changes you have not applied. Click Apply to keep them, then close. Click Close to close without them, or Cancel to stay in the popup.
Refresh Popup, then You have unsaved changes. Refreshing will discard them and reload this popup from the server. Continue?	Refreshing reloads the popup from the server and discards unsaved changes. Click Refresh to discard them, or Cancel and then Apply to keep them.
Unsaved Changes, then You have unsaved changes. How would you like to proceed?	You are moving to another step or main tab with changes you have not applied. Click Save & Continue to keep them and move on, or Discard & Continue to drop them. Click Cancel to stay. For a new object only Save & Continue and Cancel appear.
Validation Error, then the field message, such as Table name is required	You are moving on while a required field is empty or invalid. Fill in the field, which is marked with an asterisk.
Validation Error, then Please complete all required fields, or the same text followed by in the (tab name) tab, before navigating or before finishing	The step has invalid fields, and no single field message applies. Check the fields marked with an asterisk on the current step, then try again.
Table "`<name>`" not found	Opening a table from the Editor's cursor found no table with that name, so no popup opens. Check the spelling and that the table still exists, or reopen the object from the tree or the popup bar.
Something went wrong, then The content could not be displayed or This popup will close automatically...	The popup content failed to render, and the popup closes itself after about 15 seconds. Open the editor again; if it keeps failing, report what you were doing to your administrator.
Unknown user or not recorded	An Activity popover entry has no user or no timestamp. Nothing to do; the other audit values still show, and a chip names the timezone the times are shown in.

For the full list of Warehouse popup and step controls, see Warehouse workspace tour.

Dashboard, tree and search

You see	What it means and what to do
Loading tables or Loading menu	The Warehouse Dashboard or the tree is still loading. Wait; the cards or the tree replace the placeholder when loading finishes.
Data refreshed	The tree has just been reloaded from the server. Nothing to do; the list is up to date.
No warehouse objects found, then Create tables or transformations from the menu or use Add New in the header.	The Warehouse has no tables or transformations yet, and the notice shows even while a search is active. Create an object from the New menu in the tree toolbar or from Add New in the header.
No results found or No matches for "{query}" or No results for "{query}"	The active search matched no table, transformation or group, so every card is hidden. Change the search text or click Clear search.
Showing first 50 results	The search found more matches than the list shows: it stops at 50 and the count beside the search box reads 50+. Type more characters to narrow the search.
No items to display	The filters you set leave no rows in the tree. Clear a category or click Reset to see the tree again.
No types or No models or No sources	A filter category has nothing to pick from. Pick another category, or create the missing table type, logical model or semantic source first.
No tables in this group	A group card has no tables to list. Add a table from the New menu or Add New, or switch grouping.
Pending (badge)	The table is not deployed yet, and a transformation shows it until it is finalized. Deploy the table from its popup or its right-click menu, or finalize the transformation.
Skipped (badge)	The transformation is finalized but its schedule is off, so workflow runs skip it. Turn the schedule on.

Row-level security

You see	What it means and what to do
Roles not in table permission groups: X, or Columns not found in table: X	The RLS filter names roles or columns that the table does not have. Add them to the table's permission setup, or remove them from the filter, then save again. See Warehouse permissions and row-level security.
Invalid RLS script: X, or a refusal such as Forbidden keyword "X" found in script, Semicolons are not allowed, Line comments (--) are not allowed, INTO OUTFILE is not allowed or FORMAT clause is not allowed	The RLS filter takes one SELECT statement: no semicolons, no comments, no write clauses and no forbidden keywords. Remove the named part of the script, then save again.
RLS enabled successfully	The protection switch was turned on and applies straight away, not with the step's save. Every permission group now sees only the rows its rules allow.
RLS script generated successfully	The script preview was generated from your rules on the server; viewing it saves nothing. Check the script, then click Apply to save the step.
RLS settings saved successfully. or RLS settings updated successfully.	The rule set was stored: a new table's set is saved whole, and a later save replaces an existing table's set. Nothing to do.
ClickHouse query failed	On a deployed table the script is run against the table before saving, and the table could not execute it. Simplify the script, check the column names and functions it uses, then save again.
Please check the RLS configuration.	A check on the rules failed, shown as a Validation Error. Review the rule groups and fields, fix what the refusal names, and save again.
Failed to save RLS settings.	The save itself failed. Retry once; if it repeats, reopen the popup, check the rules and try again later.
Roles without explicit rules see everything	The note appended to the generated script: a permission group that no rule block targets is not restricted and sees every row. Add a rule block for every group that must be limited.
Switch to Manual Editing, then Are you sure you want to proceed with this change? This may affect your data integrity.	The editor is about to switch to Manual and starts from the last generated script. Confirm only if you intend to write the SQL by hand.
Your manual script will be lost. (confirmation Switch to Auto Builder)	Switching the editor back to Auto discards your hand-written SQL. Copy the SQL first if you need it, then confirm.
Permission Groups Required, then You must add at least one permission group before you can configure Row Level Security. Add permission groups in the General tab to proceed.	The step has no visible permission group to filter; groups hidden from you are filtered out and the admin group does not count. Add a permission group on General, then return to RLS.
Discard unsaved changes?	The expanded RLS view is closing with unsaved edits, which exist only as a draft. Confirm to drop the draft, or keep the view open and save.

Tables and columns

You see	What it means and what to do
Table name is required	The table name is empty. Type a name.
The max name length is 211, current length is N	The name is too long. The length counts encoded characters, so special characters use more of the limit. Shorten the name.
At least one logical model is required	Pick at least one logical model in the General step.
At least one source system is required	Pick at least one source system in the General step. If none exists yet, create one first; see Semantic sources, source systems and logical models.
The table with name X already exists	Another table has that name. Choose another name.
Table name cannot contain double quotes	Remove the double quotes from the name. The same message appears for a backtick, so remove those too.
Cannot remove permission group(s) from table "X": it is used in the following Minds: [...]. Remove it from those Minds first	The listed Minds use this table, and the group you are removing is their owner role. Remove the table from those Minds, then remove the group. See Link data to a Mind.
Please add at least one custom column.	The Columns step holds only system columns. Add a column of your own.
At least one user-defined column must be marked as a Primary Key.	A Static table needs a primary key. Tick PK on the column that identifies each row.
Column name cannot be empty (Row ID: N)	A column row has no name. Name it. N is the number of that row.
System reserved names found: ...	A column uses a name the system reserves. Rename it.
Duplicate column names found: ...	Two columns share a name. Names are compared without regard to case. Rename one of them.
This is a system reserved name or Column name must be unique	Shown as a tooltip on the warning icon next to a column name. Rename the column.
Dots are risky in column names - Consider renaming. SQL reads them as table.column.	Shown under a column name that contains a dot. Rename the column before you save.
A column named "X" already exists on table "Y".	Another column on the table has that name. Rename it.
TYPE_CHANGE_WOULD_NULL: N values of "X" cannot be converted to Y (e.g. 'v'); truncate the table first and reload after the change	Existing values cannot survive the type change. Truncate the table, change the type, then reload the data. See Define table columns.
PII cannot be enabled on view tables	PII cannot be set on the columns of a View.
PII cannot be enabled on locked column "X"	A locked column cannot be marked as PII.
No columns found, or No columns were detected in the SQL script.	Import from SQL found no columns. Check that the query returns columns.
Import Failed	The query did not run. Read the message, then fix the query or use Fix with AI.
Cannot fix query, then Save general settings first, then try Fix with AI again.	Fix with AI needs a saved table. Save the General step first.
Fix with AI failed	The AI could not produce a fixed query. Try again, or edit the query by hand.
This index name is already in use. Please choose a different name.	Index names must be unique on the table. Choose another name.
Index "X" must have at least one column	An index is empty. Add a column to it, or remove the index.
An index's type and granularity cannot be changed; create a new index instead.	The index type and granularity are fixed when the index is created. Create a new index with the settings you need.
Index name "X" may not contain double quotes, backticks, backslashes or control characters, and has at most 128 characters.	Rename the index.
Indexes saved successfully. or Indexes updated successfully.	The first save of the Indexes step reads saved, and a later one updated. Nothing to do; the indexes are part of the table definition.
Index "X": "Y" is not a column of "Z"; its columns: ...	The index names a column the table does not have, and the list that follows is the table's own columns. Correct the column in the index, or add the missing column to the table first.
Index "X": "Y" is an ALIAS column of "Z", computed when it is read; index the stored column it reads instead.	A column computed when it is read cannot carry an index. Index the stored column the computed one reads from.
Year isn't available yet. (or any partition option other than Day)	Only Day can be saved as the partition frequency today. Choose Day.
Disable Store History?, then This will drop and recreate the table. All existing historical data will be permanently lost.	Turning off Store History drops and recreates the table, and its history is lost. Confirm only if you accept that.
System columns cannot be edited. or This row is locked and cannot be edited.	The cell belongs to a system column or to a locked row, so it stays read-only. Leave it as it is; the PII Domain on Source ID and the Permission Group on Delete Flag stay editable.
Some columns cannot be deleted, with (system column) or (used in transformation)	The delete left blocked rows in place. Check each reason; a column used by a transformation must be released from it first.
Table "X" has system column(s) that cannot be deleted: ...	The batch asked to delete system columns, and the server refuses. Remove only your own columns.
Table "X" requires at least one primary key column.	The save would leave the table without any primary key. Keep or add a primary key column before saving.
Column "X" cannot be a primary key: a Dictionary's primary key is "Y Key" and is fixed when the table is created.	A Dictionary's key is set when the Dictionary is created and cannot be swapped. Keep the Dictionary's own key column.
Primary key of table "X" cannot change while it is deployed (column "Y"). Drop the table first, then change the primary key and deploy again.	A deployed table's key is frozen. Drop the table, change the primary key, then deploy again.
AI sample features are disabled for tables with PII columns	The AI comment and primary-key helpers do not run on a table that has PII columns. Remove the PII tags first if the table does not hold personal data.
Cannot remove column "X": it is used in Minds: [...]. Remove that column from those Minds first, or the same with permission group(s) from column "X"	A Mind uses this column, so the delete or the permission change is refused. Remove the column from those Minds first.
No permission groups added to table	The table has no permission groups, so none can be assigned to a column. Click Add in General and add groups under Permission Groups first.
The columns have been updated successfully, and step saves read Column changes saved successfully., Column changes updated successfully. or Columns saved successfully	The column batch (creates, updates and deletes) was saved. Nothing to do.
Validation Error, then Please check the columns configuration. or Please fix column errors	A step save check failed and the toast names the first problem found. Fix the flagged column rows, then save or apply again.
Failed to save columns. or Failed to save indexes. or Failed to save mapping data. or Failed to update View or Failed to update view dependencies	The save request failed on the server. Read the error text, check the named problem, and try again; your changes stay in the grid.
Changes Reverted, then All changes in the columns tab have been reset.	Revert dropped every change made since the last save. Nothing to do; edit the cells again if this was not intended.
Successfully saved, then Column changes saved successfully. Keep in mind that dot was used for column name(s) which is tricky and usually better to avoid as SQL reads them as table.column.	The save succeeded but introduced a dotted column name; the caveat replaces the plain success text. A saved dotted name cannot be renamed back, so drop and re-add the column if it must change.
No matches found	The permission-group search found no group with that text. Clear or change the search text.
No description provided.	The column has no description yet, shown in the comment popover's view mode. Click the edit control and write one.
No columns defined.	The grid has no columns: a Static table with none yet, or a View whose query returns none. Add a column, or check the view's query on the Query step.
Table ID is required for saving columns. or Table ID is required for saving indexes.	The save ran before the table itself was created. Save the General step first, then save again.
Save general settings first	The column import button is disabled because the table or dictionary has not been saved yet. Save the General step first, then reopen the import.
N column(s) imported successfully.	The detected columns were added to the grid as temporary rows. Review them and click Apply to keep them.
An error occurred while running the query.	Running the SELECT in the import window failed with no other details. Check the statement and run it again.
Enter to import, Shift+Enter for new line	In the Dictionary import popover, Enter runs the import while Shift+Enter starts a new line. Use Shift+Enter while editing multi-line SQL.
Column Types Updated, then Column data types have been recalculated based on the current query.	The Recalculate Column Types action refreshed the types from the current query. Review the types; if one still looks wrong, check the view's query.
The admin group has full access to all columns by default.	The admin group is in every column's permissions, cannot be removed, and is hidden from the picker. Nothing to do; admin access applies automatically.
Search PII source columns… or None	The PII Source picker searches source columns that carry a PII domain, and None leaves the column without a PII source. Pick the source column, or leave None.
Columns not validated	The view's query is not validated, so the column changes are not saved. Validate the query on the Query step, then apply the column changes.
General settings created successfully. or General settings updated successfully., and Static created successfully or General settings saved successfully	The General step was saved; on a first save the object was created. Continue with the next step.
Failed to save general settings. or Failed to save general information	The save did not complete; the toast carries the reason when it has one. Read it and try again.
Historical versions stored or History not stored, and Retention policy active or Retention disabled	The state labels of the Store History and Enable Retention switches; retention stays greyed out while Store History is off. They only report the state.

Dimension history

You see	What it means and what to do
Table does not exist, Table is not dimension, Table is not deployed, Table has not store_history enabled, Source system doesn't exist in relation or Schedule active etls does not exist	The history step was skipped: the table must exist, be a Dimension, be deployed and keep history, and the source system must have a transformation with its schedule on. Fix the named state on the table's General step, then run again. See Dimension history.
Table X does not have store_history enabled, Table X is not deployed or Table X is not a Dimension table (type: Y)	A history run stopped because the table is not a deployed Dimension with Store History on. Fix the named state on the table, then run again.

Deployment and previews

You see	What it means and what to do
Table Not Created, then Please save the table first to preview data, or the same notice for a Dictionary, Static table or View	Preview needs a saved object. Save the General step first.
Table must be deployed to preview data	Shown when you hover over the disabled Preview tab. Click Deploy first.
Dictionary must be deployed to preview data	The Preview tab stays disabled until the dictionary is deployed; the text shows when you hover the disabled tab. Deploy the dictionary first.
Load the table preview to get started, or the same line for a Dictionary, Static table or View	The preview loads nothing until you ask. Click Refresh to load the rows.
Query failed, with the reason under it, or Failed to load the table preview	The preview query did not run (the last good result stays on screen), or the load failed with no specific reason. Read the reason or click Retry, then check that the object is deployed and that you can read it.
Dimension Table Not Created, then Please save the Dimension table first to view settings	The Settings tab needs a saved table. The type in the title follows the table you have open, for example Fact. Save the table first.
Dimension Table Not Deployed, then Deploy this Dimension table to access statistics and transformation runs. Deployment creates the table in the warehouse with your current configuration.	Statistics and transformation runs need a deployed table. Click Deploy in the Settings tab.
Table deployment failed, or Table partially deployed. A Dictionary shows Dictionary deployment failed or Dictionary partially deployed, and a Static table shows Static table deployment failed.	The deployment did not finish. The message under the title gives the reason. Fix that problem, then click Deploy again.
Table does not have primary key	A Static table needs a primary key column, and so does a Refreshing or Appending view. Add one in Columns, then deploy again. Standard and Parametrized views do not need one.
Primary Key Required, then This table must have at least one primary key column before it can be deployed.	A Static table has no primary key. Click Go to Columns, define the key, then deploy.
Table is already deployed	The table is already in the warehouse. Nothing to do.
Unable to truncate, the table is not deployed, or Unable to purge deleted rows, the table is not deployed	Deploy the table before you truncate it or purge its deleted rows.
Failed to truncate partitions	The truncate did not finish. Read the message, then try again.
Failed to drop table	The table was not dropped. Try again.
Cannot query table "X": it is not deployed, or Cannot insert into table "X": it is not deployed	The action reached the warehouse before the table was created there. Deploy the table, then try again. See Deploy, run, truncate and monitor tables.
Column "X" has data type "Y", which resolves to the ClickHouse "Nothing" type and cannot be used in a table	A column resolved to no data type, so the table cannot be deployed. Choose a concrete data type for the column, then deploy again.
Cannot (action): Standard views are not stored on disk, or the same with Parametrized views	The action you started, such as truncate, does not apply to a view that stores no data. See Views.
This Dimension table is not deployed. Deploy to enable statistics and transformation runs., or the same notice for a Static table (Deploy to enable preview and statistics.) or a Dictionary	A saved object that is not in the warehouse yet: nothing loads until it is deployed. Click Deploy in the banner at the top of the tab.
Table deployed successfully, Dictionary deployed successfully, Static table deployed successfully or View deployed successfully, then ... has been deployed to the warehouse	The deployment finished and the object is in the warehouse. Nothing to do; statistics, runs and Preview start working.
Partitions truncated successfully, then {N} partition(s) have been truncated	The selected partitions were removed and the table stays. Nothing to do.
This table cannot be truncated by partition., Pick a source system, then choose the partition dates to truncate., Pick a source system and the target storage to truncate., Pick a source system to truncate. or No source systems available	The Truncate Partitions dialog explains which way this table can be truncated. Pick a source system, and the dates or storage target where offered; if none is listed, check the table's source systems.
Select a source system to view its partition dates., No partition dates for this source system. or This table has no partitions to target.	The partition dates panel is waiting for a source system; the selected one has no dates, or there is nothing to target. Pick another source system, or close the dialog.
You are about to truncate {N} partitions from source system "X"., then This action cannot be undone.	The final confirmation before data is removed for good; the button shows a busy state while the truncate runs. Continue only if you accept the loss.
Clear the current (main) table data., Clear the historical (versioned) data. or Clear both main and history data.	What each Truncate Target option clears. Pick the scope you need, then confirm.
No transformation runs found	No production run has written to this table yet. Run one of its transformations; the run then appears here.
Drop this table from ClickHouse?, then Drop table, with All data is permanently deleted., The definition stays, so you can deploy again. and Anything that depends on it is not dropped and will break until you fix it or redeploy the table.	The drop removes the stored data for good; the definition stays and dependants break until fixed. Check the Dependants tab first; continue only if you accept the loss.
Table dropped from ClickHouse or The table has been dropped from the database	The drop finished and the table can be deployed again. Nothing to do; deploy again when you need it.
Static Table Not Deployed, then Deploy this static table to access preview and statistics. Deployment creates the table in the warehouse with your current column configuration., or Table Not Deployed, then Deploy this table to access data mapping. Deployment creates the table in the warehouse with your current column configuration.	The saved object is not in the warehouse yet. Click Deploy; statistics start loading and Preview opens after it.
View deployment failed or View partially deployed	The deploy did not build the view; the description carries the first server message. Fix the cause and deploy again.
Failed to truncate table	The truncate request failed. Read the message and try again.

Downloads and exports

You see	What it means and what to do
Excel supports up to 1,045,000 rows, this export has more. Use CSV, TSV or JSON instead.	The download was refused because the table holds more rows than an Excel file can take. Download the table as CSV, TSV or JSON instead.
Export failed	The download stopped; the toast carries the reason when the server sent one. Read the reason, fix it, then download again.

Views

You see	What it means and what to do
Refresh Interval is required for Refreshing and Appending views, Refresh Interval Unit is required for Refreshing and Appending views, or Minus N Days is required for Appending views	Fill in the refresh settings in the General step for the view type you chose.
Offset Unit is required when Refresh Offset is set, or Refresh Offset is required when Offset Unit is set	Fill in both offset fields, or set Offset Unit to None.
Primary key required. Define a primary key column before this view can be deployed.	A Refreshing or Appending view needs a primary key column. Add one in Columns, then deploy.
Query must be validated before creating view	Validate the query first: open the Query step, click Validate, fix any problem shown under Error Details, then create or deploy the view. See Views.
The query returns duplicate columns: X	Two output columns share a name. Give each column its own name with an alias, then validate again.
Parameter values cannot be null. Null parameters: X, or Empty string values are not allowed for numeric parameters: X	Fill in each parameter with a value of the right kind. Numeric parameters cannot be empty.
Appending view query must include the required parameter	An Appending view's query must include the `{sync_n_days:Int32}` parameter. Add it, then validate again.
Every table/view used in query must be in admin_Lake or admin_WH database or be an expression. Found invalid database(s): X	The query reaches a database the platform cannot read. Use only Lake and Warehouse tables in the query, then validate again.
Didn't manage to cancel, X refresh has already finished	The refresh finished before the stop reached it, so there is nothing left to cancel. Check the refresh card for the last result.
View Not Deployed, then View must be deployed to view settings or View needs to be deployed to be used in the warehouse	The view is saved but its stored objects are not built yet. Click Deploy in the banner, or deploy from the view's right-click menu in the tree.
Changing view type will result in data loss in next steps.	While editing an existing view, changing View Type can lose what the later steps set up. Review the following steps again after you apply the change.
must be greater than 0 or must be 0 or greater	Shown with the Refresh Interval or Refresh Offset field. Set a whole number of 1 or more, or 0 or more for the offset.
Query is required, Name is required, Type is required or Value is required	A parameter row on the view's Query step is incomplete, or the query field is empty. Fill the named cell, then validate again.
View validation cancellation requested	The Stop request was accepted and the running check is being stopped. Wait a moment; nothing is saved by the check.
Loading the view preview…	The preview load is running. Wait, or click Stop to cancel; a cancelled load is not an error.
View query update must include all existing primary key column(s)	The new query no longer returns a column the view uses as its primary key. Keep that column in the SELECT and save again.
View query updated successfully.	The query was saved to the view. Move on to the next step.
Confirm Truncate Action, then Are you sure you want to truncate this view? This action will permanently delete all data in the view and cannot be undone.	Truncation deletes the view's stored rows for good. Confirm to clear the rows, or close the dialog to keep them.
Table truncated successfully	The truncate finished and the stored rows were cleared. Nothing to do.
View Statistics (cards Size, Rows, Partitions, with Refresh, Truncate and Drop)	The strip summarising the view's stored table, one card per metric (a card shows - while its value is unavailable). Refresh reloads the numbers; Truncate clears the stored rows; Drop removes the stored table while keeping the definition.

Dictionaries

You see	What it means and what to do
Cannot deploy Dictionary "X": a Dictionary must have at least one query.	Add a query, then deploy again.
A Dictionary must have at least one query. Removing the last query is not allowed.	A Dictionary keeps at least one query. Add another query before you remove this one.
Query must include "Source ID" field (exact match required), or The query must have a Source ID field	The query must return a column named Source ID, spelled exactly.
The Source ID field must be a String type. Use CAST or CONVERT	Convert the Source ID column to text with CAST or CONVERT.
"Source ID" must be unique for each row in the query result	Two rows share a Source ID value, and empty values count as one value. Give each row its own value.
"SOURCE_ID" should be Unique for each "SOURCE_SYSTEM_ID"	Two rows carry the same Source ID for the same source system. Give each row its own Source ID per source system, then load the rows again.
Unknown dictionary source key(s): "Source ID"='x', "Source System ID"='y' followed by Each "Source ID" and "Source System ID" pair must exist in the dictionary main table.	The rows name a pair the Dictionary does not contain. Load that pair into the Dictionary first, or fix the values, then try again.
Too many records: the maximum allowed is 15,000	A dictionary query can return at most 15,000 rows. Narrow the query.
Query cannot be empty, or Query must be a SELECT statement	Write a SELECT query.
All available data sources are already in use. Each data source can only be used once.	Every source system already has a query. Edit the existing query instead.
Please add at least one data source before proceeding, or Please validate all queries before proceeding	Add a data source, and validate each query, before you leave the Queries step.
Retries: -1 is the only negative value allowed (it retries indefinitely)	Enter -1, or 0 or more.
Refresh Offset: must be 0 or greater	Enter 0 or a larger number.
Refresh interval must be greater than 0	Enter 1 or more.
AI fill features are disabled for tables with PII columns	The table has a PII-tagged column, so Fill with AI is off for the whole table. Fill the rows by hand.
Dictionary name is required	The Name on the General step is empty, so the step cannot be saved. Type a name, then save again.
Dictionary created successfully or General information updated successfully	The General step was saved; the first save creates the dictionary and locks its name. Continue with the next step.
Dictionary Table Not Created, then Please save the dictionary table first to view settings, or Static Table Not Created, then Please save the static table first to view settings	The Settings tab needs a saved object. Save it first, including its General step, then reopen the tab.
No sources yet, No query selected, Select a data source to preview the new query., No source systems available or No sources match	The Queries step is empty: add a data source, pick a source system, or clear the search. If no source system exists yet, create one first.
Error validating query	The validation call failed and no other reason came back. Run the validation again.
Query Difference Checker, with Current Query and AI Suggested Query	An AI-suggested query is waiting for review. Click Apply Changes to use it, or Close to keep the current query.
No data available, then This query executed successfully but did not return any rows.	The query passed its checks and the result preview opened, but it returned no rows. Change the SQL if you expected rows, then validate again.
No query history yet	No saved versions exist for this query yet. Save the queries and open History again.
Queries saved successfully or Failed to save queries	The Queries step saved, or the save did not go through. Read the reason if one shows and retry.
Scheduled, Running or Disabled (status badges in Refresh Settings)	The refresh schedule's state drives which actions appear: Stop Schedule or Synchronize while Scheduled, Cancel Refresh while Running, Start Schedule while Disabled. Click the matching action; a manual Synchronize does not change the plan.
Cancelled (badge next to Refresh Settings)	A refresh was cancelled; it is not an error. Nothing to do; the badge disappears after a few seconds.
Loading view refresh data... or No view refresh data available	The refresh panel is loading, or the object has no refresh record to show. Wait for the next reload; if it stays empty, check that the object is deployed.
Error (chip in the refresh details)	The last refresh ended with an error. Click the chip to open Error Details with the full message, and use Copy Error to copy it.

Static tables

You see	What it means and what to do
Primary key field 'X' is required	A row has no value in its key column. Fill in the key before you save.
Excel upload failed	The file did not load. Check that its columns match the columns of the table.
First row must contain non-empty column headers	Only the first worksheet is read, and its first row must name every column. Fill in the headers, then upload again.
Excel exceeds the maximum allowed rows. Maximum: N, provided: M	The sheet has more rows than allowed. Remove rows or split the file, then upload again.
Failed to parse the provided Excel file: X, or No worksheet found in the Excel file	The file could not be read as a workbook. Check that it is a valid Excel file with at least one worksheet, then upload again.
Sync Failed, then Failed to synchronize data. Please try again.	Refreshing the table's data failed. Try again.
Purge Failed, then Failed to remove deleted rows. Please try again.	Removing the deleted rows failed. Try again.
AI fill failed, then Failed to fill data with AI. Please try again.	The AI fill did not finish. Try again.
AI fill completed, then AI processing completed but no data changes were made.	The AI made no changes. Rephrase your request and try again.
Static list name is required	The General step has no name, so the table cannot be saved. Type a Name and save again.
rows must contain at least one row	The mapping save carried no rows. Add or change a row, then click Apply again.
Value required for non-nullable column: X, Invalid numeric value: X, Unknown column: X or Required column missing: X	A saved row or file does not match the table's columns: fill the named column, correct the value, or match the file's headers, then save or upload again.
Remove All Deleted Rows?, then This will permanently remove N deleted row(s) from the database. This action cannot be undone.	The confirmation before deleted rows are purged for good (Dictionary and Static table). Confirm only if you accept the loss; otherwise cancel.
Deleted rows removed permanently.	The purge finished and the deleted rows are gone. Nothing to do.
Excel upload successful, then Your data has been imported.	The file was imported into the dictionary, or replaced the static table's rows. Review the rows; previous rows stay viewable under the Deleted toggle.
Synchronizing, then Refreshing data from source..., and Data synchronized successfully	A refresh from the object's sources started and finished. Wait for it; the grid reloads with the latest rows.
Select rows to use AI fill, and AI Data Assistant, then Describe what information you want AI to fill for the N selected row(s).	The Fill with AI button needs selected rows; the dialog asks what to fill in them. Select rows, describe the values, then click Fill Data.
AI fill successful, then Updated N row(s) with AI suggestions. or Updated N row(s) and added M new row(s) with AI suggestions.	The assistant filled the selected rows. Review the values in the grid, then click Apply to save them.
Mapping data saved successfully	Apply saved every row you touched. Nothing to do.

Transformations

You see	What it means and what to do
Table is required, Source System is required or Pattern is required	Fill in the field in the General step.
Synchronize days are required for the selected pattern	A periodic pattern needs a number of days. Enter it.
Loop Increment Value is required for the selected pattern, or Loop Increment Value must be at least 1	Enter a loop increment of 1 or more.
Full Reload Start Date: Use the format YYYY-MM-DD	Enter the date in the format YYYY-MM-DD.
Full Reload Start Date: Date must be between 1970-01-01 and 2106-02-07	Enter a date within that range.
The transformation with the name X already exists.	A transformation with the same table, source system and pattern exists. Add a Suffix to the name.
Changing the pattern is not allowed., or Changing the table is not allowed. The transformation: X is linked to table: Y.	The table and pattern of a saved transformation are locked. Create a new transformation for the other table or pattern.
Query not validated, or * Query must be filled to proceed	Write the query, then click Validate before you leave the Query step.
Query Validation Error	The query failed. Read Error Details, then fix the query, or click Fix with AI.
Query cannot include "Snapshot Datetime" column	Remove the Snapshot Datetime column from the query result.
Prompt is required, or Failed to generate with AI	Type a description in Generate with AI, then try again.
* Every active column must have at least one mapping to proceed, * Type incompatibility: X, or * Mandatory columns are not mapped: ...	In the Mapping step, map every active column, use matching types, and map the mandatory columns.
Column Already Mapped, then X is already mapped to "Y". Each source column can only be mapped to one target.	A source column can feed one target only. Pick another source column.
Target table not deployed	Deploy the target table, then run the test again.
No test run exists for transformation: X. Run a test before finalizing.	Finalize needs a finished test. Run the test, wait for it to finish, then finalize.
You can't run this transformation until its target table is deployed. Deploy the table first, then run a test.	Shown in place of the test controls while the target table is not deployed. Deploy the table, then click Test Now.
Test run required to complete transformation, then Execute a test run to verify your transformation logic and preview the output before confirming.	No finished test exists yet: a new transformation, or one whose query or columns changed since its last test. Click Test Now and run one.
The last test (etl log N) has status "Aborted"; only a Finished test can be finalized.	The latest test did not finish successfully. Run the test again, then finalize.
Test is running for transformation: X, Test is already running for transformation: X, or Test is running for transformation, wait or abort before updating: X	A test is still running. Wait for it to finish, or click Abort in the Validation step.
Failed to start test run. Please try again.	The test did not start. Try again.
Failed to finalize transformation	Read the message, run the test again, then finalize.
Cannot delete transformation(s) [X]: a run is in progress. Abort it first.	A run still holds the transformation. Abort the run, then delete the transformation.
Loop increment value (N) cannot be greater than synchronize days (M).	The loop step is wider than the run window. In Run Parameters, lower the loop increment or raise the synchronize days, then run again.
Etl log id: N is not running.	The run you tried to stop already ended. Refresh the run list; there is nothing to abort.
Failed to run transformation, or Failed to execute transformation	Read the message. Running a transformation needs Execute/Abort Warehouse Objects.
First make table selection	The Source System field waits for a table to be chosen, because source systems belong to the table. Choose a Table first, then pick from the source systems it lists.
Full Reload When Partition Empty is required for the selected pattern	The switch has no value set for a periodic pattern. Set it on or off, then save again.
fill required fields in configuration	A required value inside the Configuration card is missing, such as the Table, Source System or Pattern. Open it, fill the fields it lists, then save again.
Failed to register Transformation or Failed to update Transformation	The save did not go through. Read the message, fix the problem, then save again.
An error occurred while validating the query or An unknown error occurred	The validation request itself failed, or the error window opened without a stored message. Read the details, fix the query or use Fix with AI, then validate again.
Query saved successfully	The query and its parameter values were saved. Continue to the Dependencies step, or keep editing.
Validated or Not validated	Whether the query's last check succeeded; the badge hides while the query is empty. After Not validated, click Validate before saving or moving on.
No parameters provided	The transformation query has no parameters. Write a `{name:Type}` placeholder in the SQL to create one.
Loading column mapping	The Mapping step is fetching its columns. Wait; the table appears when loading finishes.
No columns match your search. or No columns found.	The search matches no row, or nothing in the picker matches; columns other rows already use are not listed, and an unattached side reads Select source columns. Clear or adjust the search, or click the side and pick a column.
Fractional part will be lost during casting, Value might not fit in the target type range or Precision loss may occur during casting, and Cannot cast negative values to unsigned type, Impossible to cast between these types or Cannot convert NULL value to non-Nullable type	The cast between the attached columns has a problem. The first group are warnings that do not block the save (accept them, or attach a different column); the second group are errors that block it (attach a different column, or change the column's type on the table).
Columns automatically mapped, then These columns were mapped for you. Finish mapping any missing fields, then confirm to save.	The platform matched columns on load and needs a confirmation. Finish missing fields and click Confirm; a save or Next also counts as the confirmation.
Column mapping saved successfully	The save went through. Nothing to do.
New, Updated or Removed (mapping row badges)	The state of a mapping row: a column the platform did not match, a row changed since the saved mapping, or a column the query no longer returns. Finish New rows by attaching columns; review Updated rows; Removed rows need no action.
No transformations configured for this table.	The table has no transformations yet. Click Add Transformation to start one, with the table already chosen.
Run transformation, Enable schedule, Disable schedule, Duplicate transformation, View details or Delete transformation (card actions)	The card's actions appear only when you point at the card, and Run, the schedule toggle and Duplicate only on a finalized transformation. Finalize the transformation first if run, schedule and duplicate are missing.
Delete transformation, then Are you sure you want to delete "{name}"? This action cannot be undone.	The final confirmation before the transformation is removed for good. Continue only if you accept the loss.
Failed to delete transformation	The delete did not go through; a server reason replaces the fallback when available. Read the message and try again.
Test run started successfully	The test request was accepted and the run started. Watch the Latest Run card or the test log for its status.
Abort Transformation Run, then Are you sure you want to abort this transformation run? This action cannot be undone.	The confirmation before stopping a test or a production run; a successful stop is reported with Test run aborted successfully or Transformation run aborted successfully. Confirm to stop the run, or dismiss to leave it running.
Failed to abort test run or Failed to abort transformation run	The stop failed or was refused and no reason came back. Read any reason shown, refresh the list, and try again; the run may still be executing.
Failed to refresh transformation runs	The run list could not reload. Click Refresh data to try again.
No test runs found	The test log has no runs to show. Run a test with Test Now.
Confirm transformation after reviewing results, then Review the test run output to verify your transformation before confirming it for production.	The newest test finished successfully and the transformation is not finalized yet, so the step asks you to review the output first. Click Show Results, review both sides, then finalize.
Transformation Error Details or Transformation Run Details	The dialogs for a run: the error stack behind Show Error, or the run's fields behind double-clicking its row. Read them; while the run is still going, use Abort Run to stop it.
Review source and target first to unlock., then Confirm and complete the transformation.	The Finalize step is locked until you open Source Table and Target Output once each. Open both, then click Finalize in the sidebar or Finalize Transformation in the footer and confirm.
Are you sure you want to finalize this transformation? This action will complete the transformation process and cannot be undone.	The finalize confirmation; the action cannot be undone. Check both reviews before confirming; if the request fails, the dialog stays open with the reason.
The transformation has not been finalized yet. Are you sure you want to close without finalizing? You can always come back to finalize it later.	You are closing the Test Results drawer before finalizing. Click Close Without Finalizing to close and finalize later, or stay to finish.
Transformation finalized successfully	The finalize succeeded; Execute Now becomes available on the Execution tab. Nothing to do.
No source results available or No target results available, then This test run did not return rows for the {label} output. You can still review the SQL query to verify the transformation logic.	The test returned no rows for that side. Click View SQL Query and check the logic, then adjust the query and run another test.
Transformation run started successfully	The run request was accepted and the run is queued. Nothing to do; the run appears in the Run Log and the list reloads.
Running (badge next to the Run Log)	At least one run in the log is still going. Nothing to do; it clears when the run finishes, and the list refreshes about once a second while it shows.
All transformations writing the same table for the same source system must belong to the same workflow.	The transformation's group is split across workflows, so a finalize or a move is refused. Move every finalized transformation of the group into one workflow together, or unfinalize the rest first.
Circular dependency detected	The dependency check found a loop, so the save, a finalize or switching the schedule on is refused. Remove the dependency that closes the loop, or narrow its source systems, and save again; Revert clears the refusal.
No dependencies selected, then Choose tables your transformation depends on to give it the right upstream context., or the same sentence with view	Nothing is marked as a dependency yet. Click Manage Dependencies and mark the objects the transformation reads from.
No source system selected or Unknown source system	A dependency row has no source system, or its saved one is not among the current options; source systems are optional on a dependency. Open Manage, click Add Source on the row and pick the source systems.
+N more	More than four source systems are marked on the row and only the first four badges show. Open the row to manage the full set; the X on a badge unmarks one system.
Remove dependency	The hover control on a card that drops this dependency from the list. Click it, then save the step; Revert puts the saved list back.
Choose source systems or Optional	On a dependency row, source systems are optional: the row reads Optional until you open the picker and tick the source systems the object should read from.
Dependencies saved successfully	The marked selection was saved. Nothing further; continue to the next step.
Failed to check dependencies. Please try again.	The circular-dependency check could not run. Click Apply or Next again to rerun the check.
Invalid query settings	The settings text in the query settings dialog is empty or failed validation; nothing is saved and the dialog stays open. Correct the value the message names, then click Save Settings.
Restored version v{N}, then Save Settings to apply it.	A history restore loaded an earlier version of the settings into the dialog but saved nothing. Click Save Settings to apply it.
AI is creating your SQL query	The request is in flight and the window cannot be closed until it finishes. Wait for the result; it opens for review in Query Difference Checker.

Runs and skips

You see	What it means and what to do
Node Already Run, with the reason Transformation X has already run	The step finished in an earlier attempt of the same run, so a restart keeps its result and does not repeat it. Start a new run to run it again.
Skipped Due To Previous Error	A step this one depends on failed or was skipped. Fix the earlier step, then restart the run.
ETL is not validated, skipping	The transformation has not passed validation. Test and finalize it, then run again.
ETL is not on schedule, skipping	The transformation is not on its schedule. Turn the schedule on before the next run.
Wrong Job ID	A test run was started against a different job. Start the test again from the transformation.
Cannot run transformation, the table: X is not deployed.	Deploy the table, then run the transformation.
Skip Reason: Synchronize Option Is Disabled	The table's Synchronize switch is off, so a scheduled run skipped the table. A sync you start by hand for a single table can still start. Turn Synchronize back on in Table > General.
Skip Reason: Table Is Not Deployed	The table cannot sync before it is deployed. Deploy it, then sync again.
Skip Reason: Node Already Run	The table already finished in that run. Start a new run to sync it again.
Skip Reason: Table Not Found In STAGING_TABLE	The run cannot find the table's load setup. Refresh the data source with Sync Schema, then sync again.
Output Contains Duplicates in Source ID (a Dimension), or Output Contains Duplicates in Source ID Per Partition (a Fact)	The transformation produced two rows with the same Source ID, or the same Source ID twice in one partition. Fix the query so each Source ID appears once, then run again.
Transformation ... not found	The transformation behind the step could not be found, so the run refuses it. Check that the transformation still exists before you run again.
Could not find the earliest source date for the first run of transformation ...	The first full-history run of a periodic Fact pattern searched the source for its earliest date and failed; the text after the name tells the cause. Set Full Reload Start Date on the transformation so the first run does not depend on the search.
No Snapshot column found for transformation ... or No mapping found for Snapshot column in transformation ...	The search for the earliest date found no snapshot column on the Fact table, or the transformation does not map it. Check the snapshot column and map it on the Mapping step, or set Full Reload Start Date.

The skip and run reasons are explained in full on Skipped runs and restarts, and runs and their results are watched on Deploy, run, truncate and monitor tables.

Warehouse Builder

You see	What it means and what to do
Use "day" and map toStartOfMonth(`<date>`) AS "Snapshot Day"	A monthly partition frequency is not accepted: the refusal maps month to a day partition with a month-start expression. Use the `day` frequency and map the date with `toStartOfMonth(<date>) AS "Snapshot Day"` in the transformation.
Rows with "Delete Flag" = 1 are removed permanently	The purge step physically deletes the soft-deleted rows, and this cannot be undone. Check the marked rows before approving; they stay filtered out of normal reads until the purge runs.
two objects share the name "X".	The design lists two objects under one name, so the model cannot tell them apart. Rename one object in the design and propose it again.
"X" and its handover view "Y" are both handed over: hand over only the view.	A base object and a view of it cannot both go to the model. Hand over only the view.
Two group-bys of one name fail: prefix them ("Customer Region").	Two handed-over objects both use one business column name, so reports cannot tell the group-bys apart. Prefix the column in one object's definition so the names differ.
"X" is not built yet. Build every approved object first.	The model is created only when every approved object exists in the Warehouse. Build the missing object, then run the check again.
Owner role admin needs views over every handed-over table; "X" is handed over itself. Pick another role, or reject with a note so the design uses a view.	An admin-owned model reads handover views only, never base tables. Pick a business role, or reject the card with a note.
This design no longer passes its checks (...); reject it with a note so the Warehouse Builder proposes it again.	A re-check at approval time found a problem that appeared after the card was built. Reject the card with a note; the Warehouse Builder proposes a corrected design.
"X" is marked new, but the Warehouse table with that name (id N) was not created in this conversation; reject the card with a note so the Warehouse Builder marks it existing or changed.	The design claims to create a table that already exists in the Warehouse. Reject with a note so the object is marked existing or changed, or give the new object another name.
only X, who asked for this model, can create it. Ask them to continue this conversation.	Creation is bound to the person who asked for the design. Have the requester continue the chat so the model is created.
you need the "Add DataPrism Semantic Model" permission to create a semantic model.	The creating user lacks the DataPrism semantic-model permission. Ask an administrator for Add DataPrism Semantic Model, then create again.
the model of this session was deleted; propose the design again to start over.	The created model no longer exists, so the design session is spent. Propose the design again and create a fresh model.
the approved owner role "R" is no longer one of X's roles. Propose the design again with a role they hold.	The owner role changed between approval and creation. Propose the design again with a role the requester still holds.
This design reads tables with row-level security that the model will not apply (X). Tick "I understand" on the card to approve it.	A table's row-level security is not carried into the model. Tick I understand to approve, or reject with a note and fix the design.
This change has NOT been made. or An editor of this model rejected this change, so it was NOT made.	A change to the semantic model waits for its editors' decision, or was rejected. Wait for the decision; after a rejection, adjust and propose again, and do not retry the change unchanged.

Sync with the database

You see	What it means and what to do
Sync category changed, Primary key changed or Partition column changed	The sync dropped and recreated the stored table because its loading shape changed; the recreated table starts empty until its next load. Nothing to do when the change was planned; if you did not expect it, open the run in the DDL log and read its User column.
Table engine X could not be mapped to sync category	The sync cannot tell how the stored table was built because its engine is not recognised, so the sync fails and the run records this error. Ask an administrator to check the stored table's engine; syncs for that table keep failing until the engine can be classified.

File conversion

You see	What it means and what to do
File is not a PDF	The file does not carry the PDF signature near its start, so no conversion starts. Export the document as a PDF again and retry.
corrupt, truncated, or password-protected PDF	The file could not be opened as a PDF, because it is damaged, incomplete or password-protected. Provide a complete copy without a password.
Job 'N' not found	The job is gone (finished and cleared, or it never existed) or belongs to another conversion kind. Start the conversion again.
Job already finished with status 'X'	The cancellation arrived after the conversion had already ended. Read the result instead; there is nothing left to cancel.
Conversion is still in progress	The result was read before the conversion finished. Wait for the stream's done event, then read the result.
Conversion was cancelled, Conversion cancelled or Cancellation requested	The cancellation was requested and took effect, so there is no result for it. Start the conversion again if the document is still needed.
Conversion failed	The conversion stopped with no more specific reason stored. Try again; if it repeats, check the file.
Client disconnected	The connection went away while a conversion was running, so it stopped at its next checkpoint. Run the conversion again and keep the connection open until it finishes.

Dependencies and deleting

You see	What it means and what to do
Circular dependency: A → B. followed by Remove one of these dependencies, or narrow its source systems on the Dependencies tab.	Two or more transformations depend on each other in a loop. Remove one of the dependencies, or narrow its source systems.
X cannot depend on its own table and source system. followed by Narrow the source systems of the X dependency on the Dependencies tab.	A table cannot depend on itself for the same source system. Narrow the source systems of that dependency.
Dependants could not be determined because the check failed. Deleting may be unsafe., or Could not load every dependant, so the list may be incomplete.	The list of dependants is missing or incomplete. Check what uses the table in Explore and trace lineage before you delete it.
Some tables could not be deleted	Not every selected table was deleted. Open Failed Deletions, then click Retry delete.
Cannot remove table "X": it has transformations. Delete the transformations first	The table still has transformations. Delete or reassign them, then delete the table.
This action cannot be undone. This will permanently delete this {type}.	The row-delete confirmation; {type} is the object's kind, such as Dimension, Dictionary, View or Transformation, and falls back to item when the kind is unknown. Confirm only when the object and its data should go; the deletion cannot be undone.
Checking what depends on this...	The table delete confirmation is running the dependants check, and the confirm button is unavailable until it finishes. Wait for the check, then read the list.
Delete anyway	The confirm button when something depends on the selected tables; the check only warns and does not change what gets removed. Read the listed dependants before you confirm.
Delete Selected Item? or Delete {N} Items?, then This will permanently delete {summary}. This action cannot be undone.	The batch delete confirmation, with the count of resolved tables and transformations in your selection; {summary} counts the selection, for example 2 tables and 1 transformation. Read the counted line and confirm only when you accept that the listed items are removed for good.
All tables removed successfully, Removal partially succeeded or Removal failed for all tables	The outcome of a table delete, shown as the message title; refused tables are listed separately for retry. When only some or none went, open Failed Deletions and retry the refused tables.
Transformation deleted or Transformation(s) deleted, then The transformation node has been removed from the view	The selected transformations were removed in one delete. Nothing to do; the rows leave the tree.
Selected items deleted	A mixed selection of transformations and tables was removed completely. Nothing to do; the rows leave the tree.
Deleted {N} transformation(s), Deleted {X} of {Y} table(s) or No tables were deleted	The result lines of a mixed delete; the table line reports how many of the selected tables went. Use the counts to see what is left, then retry the refused tables.
Nothing was deleted.	In a mixed selection the transformation step failed, so the delete stopped and the tables were not attempted. Read the reason in the message, fix it (for example abort a running transformation), then try again.
Failed Deletions, then {N} table(s) failed to delete or {N} table(s) failed - click to view	The failed-table list behind the red badge on the Delete button; each row names a table and its reason. Open the list, read the reason (Copy error copies it), and click Retry delete.
Loading dependencies…	The Dependencies step is loading its list. Wait for it to finish; the step fills in on its own.
No dependencies, then This table has no upstream dependencies defined.	Nothing upstream is recorded for the table yet. Nothing to fix here; to change what the table reads, edit the transformation's dependencies.
Transformation #N or Unknown transformation	A dependency entry fell back to the transformation's number, or could not be resolved at all. Open the entry; check that the transformation still exists, then reload the popup.
Table Not Created, then Please save the table first to view its dependants, or View Not Created, then Please save the view first to view its dependants	The Dependants tab needs a saved object. Save it first, then open the tab again.
Failed to load dependants	The dependant check could not load. Click Retry; if it keeps failing, check again later.
No dependants found, then This table is not currently used by any downstream objects.	The check ran and found nothing that uses the table (a view reads This view is not currently used by any downstream objects.). Nothing to do; a failed check shows its own error state instead.
N ... you cannot access, for example 2 presentations you cannot access	Those dependants sit outside your access, so only a count is shown, never names. Ask their owners before you change the table; the row is informational and never a link.
Start new chat or View mind sources	Shortcuts on a Mind row in the Dependants list: the pencil starts a new chat, while the row opens the Mind's Sources. The Sources shortcut appears only when you can open the Mind's settings panel; otherwise use the row.
No Warehouse tables available or No Lake tables available	That column of the picker has nothing to offer; only deployed tables are listed. Check that the table is deployed.
No Warehouse tables match your search or No Lake tables match your search	The picker's search matched nothing in that column. Clear or change the search.

Source systems and semantic sources

You see	What it means and what to do
Minimum length is 2 characters, or Maximum length is 15 characters	Names of semantic sources, source systems and logical models need at least 2 characters. A source system name can have at most 15.
Description is required, Minimum length is 20 characters, or Maximum length is 500 characters	The description of a semantic source, source system or logical model must be 20 to 500 characters.
The Semantic Source with the name X already exists, The Source System with the name X already exists, or The model with the X already exists.	Choose another name. The last message appears for a logical model.
Cannot delete. The Semantic Source has referenced Source System(s)	The semantic source still has source systems. Delete them first.
Source system has transformations, or Source system has tables	A source system cannot be deleted while it is in use. Delete its transformations and tables first.
Source system deletion failed: X. These systems contain data and must be truncated before removal.	The named source systems still hold data in Warehouse tables. Truncate their data first, then delete the source systems.
Remove its N source system(s) first.	A semantic source still has source systems. Delete them first.
Semantic Source registered successfully, Source System registered successfully, Logical Model registered successfully, Semantic Source updated successfully or Source System updated successfully	The change was stored; the lists refresh on their own. Nothing to do.
Source System deleted successfully, Semantic Source deleted successfully, Logical Model updated successfully or Logical Model deleted successfully	The removal or update finished; the selection falls back to the first remaining source where one exists. Nothing to do.
Used by N tables and M transformations	The source system is still referenced, so its Delete item is greyed out; N and M are the usage counts. Delete or move those tables and transformations first.
Loading tables linked to {name} or Loading semantic sources	The panel is loading its list or a row's linked tables. Wait.
No tables use this system yet.	Nothing points at this source system. Nothing to fix; add a table from its menu if it should be used.
N transformations on tables not shown here.	More transformations read from this source system than are shown under the listed tables. Open the linked tables that are shown to view their transformations.
Semantic sources did not load	The window could not fetch the list and there is no data to show. Click Try again to reload the list.
Failed to register Logical Model, Failed to update Logical Model or Failed to delete Logical Model	The action did not go through; the form shows the reason it received, and this text appears only when the server sent none. Fix the field errors, or remove the model from its tables first, then try again.
Are you sure you want to delete this logical model? This action cannot be undone.	The Confirm Deletion confirmation for a model that nothing uses. Click Delete to confirm, or dismiss the dialog to keep the model.
No logical models found, then Create a logical model to define core entities and their relationships.	No logical models exist yet. Click Add Model to create the first one.
Failed to load logical models	The model list could not be fetched; the reason appears underneath. Click Retry.

Saved views

You see	What it means and what to do
Cannot Delete, then Predefined configurations cannot be deleted	Basic View and Source Chain are built in and cannot be deleted.
Cannot Update, then Predefined configurations cannot be updated	The built-in views cannot be renamed either. Save your own selection under a new name instead.
Duplicate Name, then A bookmark with this name already exists	Choose another name for the saved view.
Invalid Name, then Bookmark name cannot be empty	Type a name for the saved view, then save again.
Error, then Please select at least 1 object	Select at least one object before you save the view.
Cannot Load Configuration, then Please save your configuration with a name and at least one selected object before loading it	Save the view with a name and at least one selected object, then load it.
Configuration Deleted, then The configuration has been removed from bookmarks, or Name Updated, then Bookmark name has been updated successfully	The saved view was removed, or the new name is saved. Nothing to do.
Configuration Saved, Changes Saved, Bookmark Saved or Configuration Updated	Your selection or changes were stored in the saved view. Nothing to do.
Failed to Update, then Failed to update the bookmark name. Please try again., or Failed to Delete, then Failed to delete the configuration. Please try again.	The rename or removal did not finish. Try again.
Changes Discarded, then Your unsaved changes have been discarded, or Temporary Configuration Discarded, then Your temporary configuration has been discarded	Unsaved changes or a temporary view were dropped, for example when a bookmark loaded over them. Nothing to do.
Please select at least one object	The Structure Preview is empty because no object is selected yet. Drag an object from Available Objects into Selected Objects.
Unsaved Changes, then You have unsaved changes in your configuration. Would you like to save these changes before continuing?	You are closing the dialog or switching views with changes not yet saved. Save your configuration first to keep the changes; continuing discards them and loads the view you picked.
Discard Temporary Configuration?, then You have not selected any objects in your new configuration. If you continue, your changes will be lost. Continue?	You are switching away from a new configuration that has nothing selected. Continue only if you accept the discard; add objects and save the configuration to keep it.
Delete Active Configuration, then You are about to delete the currently loaded configuration. This will switch to Basic View. Are you sure you want to continue?	You are deleting the view you are using. Continue only if you want to delete it; the Warehouse then switches to Basic View.

Batch edit

You see	What it means and what to do
Save failed, then No items were updated. Check the error bar for details.	No change was saved. Open Failed Updates to see which edits failed.
Table details not ready, then N edited table(s) still need details loaded (or failed to load). Retry failed rows, then save.	Some edited tables have no details loaded. Retry the failed rows, then save.
Error: No table type selected	The popup could not resolve which table type to show, so it cannot build the grid. Click Close and open Batch Edit again from the tree.
Derived from source systems, Views do not have source systems or Table type is read-only	Locked cells: the model cell is computed from the table's source systems, a View has no source systems, and a table's type is set when it is created. Change the source systems on General if needed; nothing else applies.
Available for Dictionaries and Refreshing/Appending views, Storage statistics are read-only. or This table is deployed and cannot be redeployed from here.	More locked cells: refresh settings live on the object's own popup, statistics are shown for information only, and a deployed table cannot be redeployed from here.
Inherited from parent table, Open the transformation popup to change pattern, Read-only. Validation is managed in the transformation popup, Only for Fact periodic patterns, Query settings are available for Fact and Dimension transformations or Change mode in Query Settings	Locked transformation cells: the type follows the table, and the pattern, validation, periodic fields and query settings live in the transformation's own popup and apply only to the kinds named. Open the transformation from its cell for those changes.
Tables with ids ... not found	The request named tables that no longer exist. Close and reopen Batch Edit so the grid reloads the current tables.
Loading batch edit, Loading transformations or Loading details {enrichedCount}/{totalTableCount}…	The popup is loading its rows and details; the count shows how many table details are done. Wait; editing and saving wait for the details.
Failed to load batch edit data or Failed to load table details	The popup could not load the scoped rows, or one row's details. Close the popup and open Batch Edit again; click Retry on the failed row.
No tables found.	The scope you opened Batch Edit from holds no tables. Check the scope, or create tables first.
No transformations found.	None of the scoped tables has a transformation. Create a transformation for the table first.
Still loading details, then Wait for table details to finish loading, then save.	The save is blocked while the grid is still loading table details. Wait for the details, then click Save again.
Saved, then All N item(s) updated successfully.	Every edited row was saved; the grid reloads and rows load their details again. Nothing to do.
Partially saved, then N of M item(s) updated.	Some rows were saved and some failed; the failed rows keep their edits. Open Failed Updates, fix the cause, then save again.
No changes, then There are no changes to save.	The save found nothing left to send. Nothing needed.
Saved, but the grid could not refresh, then The changes were saved. The rows will catch up when details finish loading.	The save succeeded but the grid could not reload. Wait for the rows to catch up; close the popup and reopen Batch Edit if it stays stale.
Failed Updates, then N item(s) failed to save or N item(s) failed - click to view	The list of rows whose save failed, one entry each. Read each reason, fix the cause, then save again.
{N} table(s) failed to load details, and the Details column states Loading…, Ready or Failed	Some rows could not load their details; click Retry on a Failed row to load it again.
Deploy table?, then Deploy "{tableName}" to the warehouse with the current column configuration?	The confirmation opened by clicking a deployable Status cell; it deploys that one table and cannot be closed while the deploy runs. Confirm with Deploy; a failure shows as Deploy failed with the reason.

Relationships and diagrams

You see	What it means and what to do
Relationships can only be created between fields of the same type	Pick two fields of the same type.
Failed to create reference, then Unable to create table reference	The relationship was not created. Check that both fields have the same type, then try again.
Failed to load diagram	The diagram did not load. Click the refresh button in the diagram panel (tooltip Refresh diagram data). The message under the title gives the reason.
No tables available	The Warehouse has no tables for the relationship diagram, so the canvas stays empty. Create Warehouse tables and deploy them, then open the diagram again.
Loading diagram, Refreshing diagram, then Fetching latest data from the database..., or Diagram refreshed, then Successfully loaded latest data from the database.	The diagram is loading or reloading its data from the server; the refresh button is disabled until it finishes. Wait; nothing else to do.
Refresh failed, Refresh step failed or Failed to clear local diagram cache	The refresh stopped with an error, one step failed while the rest continued, or the local copy could not be cleared. Try Refresh from Database again; reload the page if it persists.
No logical models available	The Logical Models selector has no models to show. Create logical models, or assign tables to models, then reload the diagram data.
Table added successfully, Table already exists in this layout or Failed to add table	Dragging a table into a custom layout: it was added, it is already there (the view moves to it and highlights it), or the add failed. Try the drag again, or reload the diagram data.
No related tables found or All related tables are already on the diagram	Adding related tables found none to add: the table has no relationships, or every linked table is already in the layout. Nothing to do; create relationships or drag the tables in manually.
Table deleted from diagram successfully	The table was removed from the layout only, not deleted from the Warehouse. Nothing to do; the table still exists.
This action will permanently delete this custom diagram layout. This action cannot be undone.	The delete confirmation for a custom layout: the arrangement is removed and the tables are not. Click Delete to confirm, or Cancel to keep the layout.
Are you sure you want to reorder the diagram?, then Layout Applied	A reorder started without a chosen preset needs confirmation; when it finishes the message names the preset it used. Choose Reorder to continue, or Cancel to stop; Undo reverts the result.
No tables or columns found matching "..."	The canvas search matched no table or column, so the results list is empty. Correct the search text; search matches exact text and does not correct spelling.
Relationship created, then Table reference and relationship created successfully	A dragged relationship was saved; it starts as One to Many with the dragged field as the primary side. Change the cardinality in Set Relationship Type if needed.
Relationship Removed, Failed to update relationship or Reference remove failed	The relationship was removed, or the cardinality change or removal failed and can be tried again. The tables and their data are untouched.
Last Cached - or Refreshing…	The layouts panel header line: nothing is stored yet (the label updates after the first load), or a refresh is running. Wait for the refresh to finish.
To be deployed	The table is not created in the database yet, so its diagram node carries a status strip. Deploy the table from its popup; a deployed table has no strip.
Failed to update table position	The diagram could not save where you moved a table; when it can, it restores the previous position. Drag the table again.

Questions, answered

Where do I start when an action fails?

Read the message you were shown and find its row above. Most refusals come down to one of three things: your role lacks a permission, the table is not deployed, or a value breaks a rule for this table kind. For permissions, see Warehouse permissions and row-level security; for deploy and run basics, see Deploy, run, truncate and monitor tables.

Why won't my table deploy?

Read the message under Table deployment failed or Table partially deployed, and fix the problem it names. Static tables, and Refreshing and Appending views, need a primary key column, and a Dictionary needs at least one query. Then click Deploy again. See Deploy, run, truncate and monitor tables.

Why does a Validation Error appear when I click Next?

A required field on the current step is empty or invalid. The message names the field, for example Table name is required, and the field is marked with an asterisk. Fill it in, then click Next again.

Why can't I leave the Query step?

You can leave the Query step only when the query is not empty and has been validated. Write the query, click Validate, and fix any problem shown under Error Details. See Build, test and finalize a transformation.

Why can't I save a transformation while a test runs?

Saving is refused with Test is running for transformation, wait or abort before updating. Wait for the test to finish, or click Abort on the latest run in the Validation step, then save again.

Why do messages say my table is not deployed?

The table exists as a definition, but it is created in the warehouse only when you deploy it. Until then, actions that need stored data, such as a query, an insert, a truncate, a purge or a transformation run, are refused with a not deployed message. Right-click the table in the tree and choose Deploy, or use Deploy on its Settings tab. See Deploy, run, truncate and monitor tables.