Query Troubleshooting and Run Records

Recent runs on the Query workspace keeps the latest ten runs for the current page session. The system also records each query with its data source, language, statement, status, duration, row count, and error message. The data analysis page does not provide a separate permanent history list.

Troubleshooting order

Access: confirm that your account can view the model and run queries, and that its business domain allows access.
Model state: the model must have an available draft; metric queries also require a published model.
Query language: use SQL for relational models and read-only MDX for XMLA models.
Structure: refresh tables and columns in the data source browser and remote structure in the XMLA workspace. Copy exact catalog, cube, hierarchy, and measure names from the page.
Connection: run a query probe in Run and cache. If it fails, check the data source connection test, network, and credentials.
Draft synchronization: if the top bar shows a conflict or error, refresh and confirm the latest draft before saving or publishing again.

Common errors

Symptom	What to do
No model is available	Create a model or bind an organization data source, then confirm view permission.
Query language is unsupported	Choose SQL or MDX according to the model type.
An object does not exist	Copy the name from current structure information or the cube; for XMLA, check whether it is marked Missing.
Publishing is blocked	Open Model quality and fix each error. Review warnings before publishing.
Query times out or cannot connect	Run a query probe and data source connection test, then check the network path from the system to the database or XMLA service.

Ask platform operations for complete historical records when needed; the browser session list is not permanent history.

Quickstart

Semantic Model

Query Analysis

Metric Management

Query Troubleshooting and Run Records

Troubleshooting order

Common errors

​Troubleshooting order

​Common errors

Troubleshooting order

Common errors