Use this page when a table, chart, alert or lineage map shows a message you do not expect. Find the message in the table for its area, read what it means and do what it says.
Most messages appear as a red toast with a title and the reason. A table that has already loaded shows a red bar with Retry instead, and the rest of the table stays on screen.
Some actions need a permission you may not hold. The tables below name it where it matters. For the full list, see Permission reference.
| You see | What it means and what to do |
|---|---|
| Refresh failed, with a reason | A refresh could not reload the data. Try again. If it repeats, check your connection and the reason. |
| Date range too large, with Custom date range cannot exceed 1 year. | A custom period is longer than one year. Choose a shorter range or a preset. See Periods, filters and exports. |
| Export failed, with a reason | The download did not finish. Try again with a shorter period or fewer filters. |
| Too many exports are running at the moment | Several exports are running at once. Wait a moment, then start the export again. |
| Missing date range for log download | The export needs both ends of the period and one is missing. Set a full period, or finish the custom range, then download again. |
| Failed to download log logs: invalid file response | The download did not return a file, for example when the export is too large. Narrow the period or filters and try again; a server message may replace this text. |
| Filter options failed, with Unknown error while loading filter options | A column filter cannot load its values. Close and reopen the filter, or type in the search box instead. |
| (Empty) | In a column filter's value list, this stands for rows where the column has no value. Tick it to include blank values; leave it unticked to exclude them. |
| Reset | In a column's filter menu, the button that clears that column's filter. Click it; the filter returns to showing every value. |
| A red bar with a title such as Failed to load audit logs, and Retry | A table that had loaded cannot reload. Click Retry. If your search term caused it, change the term. |
| Last 7d shown as the period although you used another one before | A stored period that is no longer valid falls back to the default. Pick your period again. |
| An unknown error occurred | An action failed without a reason. Try again. If it repeats, ask your administrator. |
| Request failed | The server reported an error for an action without a detail. Try again. If it repeats, ask your administrator. |
| Empty | In a record's details, a field or code block has nothing recorded for this row. Read the other sections of the details for context; there is nothing to fix. |
These messages come from System Overview, Service Overview and Live Metrics.
| You see | What it means and what to do |
|---|---|
| Loading chart | The chart is still drawing for the chosen metric, period and interval. Wait for it to draw; if it stays, change the period or refresh the services list. |
| No data available, with No system metrics found for the selected time range and interval. | The total chart has no samples for the period. Widen the period or change the interval. |
| Failed to load data, with a reason | The System Overview chart could not load. Refresh the services list, or change the period. |
| Failed to load timeline, with a reason | A service's incident chart on Service Overview could not load. Change the period, or refresh the screen. |
| Loading metric | The incident's zoom view is still loading its readings. Wait for it to finish; if it stays, go back to the service and open the incident again. |
| Failed to load zoom data | The zoom view of an incident could not load its readings. Go back and open the incident again. |
| No data available, with No metric data was found for the selected time range and interval. | One service has no samples for the period. Widen the period or pick another service. |
| Failed to load service breakdown | The per-service breakdown did not load. Refresh the services list. |
| No timeline data, with The incident detail response did not include any chart points for this window. | The incident has no detailed readings. Go back to the service and pick another incident. |
| Unable to load metrics, with a reason, or Unable to load live system metrics. when there is none | Live Metrics cannot read the current memory and storage values. Wait for the next refresh, or reload the page if it stays. |
| Unable to load service health. | The service health history did not load. Reload the page later. |
| Loading day health checks | The checks of the day you opened are still loading. Wait; on failure the panel shows the reason instead. |
| Unable to load this day's health checks. | The checks of the day you opened did not load. Close the day and open it again. |
| No health checks recorded for this day. | The day you opened has no checks to show. Try another day; a day with no checks is marked No data in the strip and does not open. |
| No services are being monitored yet. | No health checks exist yet. Wait for the first checks. Ask your administrator if it stays this way. |
| No history yet | A service has no daily history yet. It fills in as health checks are recorded. |
These messages come from Query Management, Running queries, ClickHouse activity and ClickHouse storage and maintenance.
| You see | What it means and what to do |
|---|---|
| Failed to load logs | The query history or an insight view did not load. Click Retry, or shorten the period. |
| No query logs found | The query log has no runs for the chosen period and filters. Widen the Period, clear a column filter or change the search. |
| No repeated queries found, No failed queries found or No high maintenance queries found | The insight views found no queries for the period. Widen the Period; the views select queries by Last Seen. |
| Failed to load ClickHouse running queries or Failed to load PostgreSQL running queries | The running queries table cannot load. Click Retry or the refresh button. |
| Failed to load ClickHouse merges (the same message for mutations, view refreshes, the memory overview or table storage) | That ClickHouse view cannot load. Click Retry or the refresh button; if it repeats, shorten the period. |
| No merges running | Nothing is merging at the moment. Refresh later if you expect activity. |
| No mutations running | No unfinished mutations at the moment. No action is needed. |
| No refreshable materialized views | There are no refreshable views to show. No action is needed. |
| No memory metrics available | The memory overview returned nothing. Click Refresh; if it stays empty, reload the page. |
| Terminate Query, with Are you sure you want to terminate this query? | You clicked the stop icon on a running query. Confirm to stop it. The icon shows only if you hold Stop Active Queries. |
| Query terminated successfully | The stop request was accepted. Refresh after a moment to see the query gone. |
| Failed to terminate query, with a reason | The stop request failed. Check that you hold Stop Active Queries. The query may have already finished. |
| Invalid PID | The stop request carried no usable process id. Refresh the list, then stop the query from its row. |
| The process does not exist or has already finished. | The query you stopped is already gone. No action is needed. |
| The process was successfully terminated. | The PostgreSQL query was stopped. Refresh after a moment to see it leave the list. |
| Failed to terminate process pid, with a reason | The stop request failed. Check that you hold Stop Active Queries, then try again. |
| Kill Mutation, with Kill mutation id on database.table? | You clicked the kill button on a mutation. Confirm to request cancellation. The button needs Stop Active Queries. |
| Cancellation requested for mutation id on database.table. | Cancellation was requested. Refresh Mutations to check. |
| No mutation id found on database.table. It may have already finished. | The mutation has finished. No action is needed. |
| Failed to kill mutation, with ClickHouse could not cancel mutation id on database.table. | The cancellation was refused. Wait for the mutation to finish, then check Mutations. |
| Failed to kill mutation, with a reason | The kill request failed. Check that you hold Stop Active Queries, then retry. |
| Checking which tables have parts to merge... | The merge dialog is still computing its preview. Wait; Start OPTIMIZE stays disabled until the preview loads. |
| Every partition already holds a single active part. | Nothing needs merging. No action is needed. |
| A success message, OPTIMIZE started on and the number of tables | Merging runs in the background. Check Merges later. |
| Failed to start OPTIMIZE, with An OPTIMIZE run is still in progress. Wait for it to finish before starting another. | A run is already active. Wait for it to finish, then start again. |
| Failed to start OPTIMIZE, with a reason | Starting failed. Check that you hold Manage ClickHouse Maintenance, then retry. |
| Failed to load OPTIMIZE preview | The merge dialog cannot compute its preview. Close and reopen it. |
| Failed to load staging tables | The Empty staging tables dialog cannot load its counts. Close and reopen it. |
| Running workflows: name (#id) - try again when they finish. | Workflow jobs are running. Wait for them to finish. Empty tables stays disabled until they do. |
| Failed to empty staging tables, with Staging tables cannot be truncated while workflow jobs are running: jobs. Wait for them to finish or abort them, then try again. | Jobs started after you opened the dialog. Wait for them to finish, or stop them in Workflows, then try again. |
| Staging tables emptied, with Truncated and the number of tables | Emptying finished. If some tables failed, the message names them with their errors. Check those tables and try again. |
| Failed to empty staging tables, with a reason | The request failed. Check that you hold Manage ClickHouse Maintenance, then retry. |
| PostgreSQL view unlocked, PostgreSQL view is already unlocked or a countdown such as 5 more taps to unlock PostgreSQL | Tapping Queries ten times unlocks the hidden PostgreSQL table; the unlock stays in this browser. See Running queries. |
| Could not load table storage | The table cards in History cannot load. Refresh. |
| No tables match your search, with Try a different term or clear the search field to show all tables again. | No table matches the search. Change the search. |
| Could not load more tables | Scrolling History could not load more tables. Scroll again, or refresh. |
| No tables with data parts | The Storage list has no rows for the current search and Hide system tables setting. Change the search, or turn Hide system tables off. |
| No buckets in range | A table card in History has no storage points for the selected period. Widen the period. |
| No databases in this range. | The History side list has no databases for the selected period. Widen the period. |
| No data, with No memory samples for this range. | The History chart has no samples for the period and interval. Widen the period or choose another interval. |
The log tables are described on their own pages: Audit, sign-in and notification logs, SSO login logs, AI, socket and PII logs, Socket logs, PII detection logs and Table DDL logs. For usage figures, see Mind Analytics.
| You see | What it means and what to do |
|---|---|
| Failed to load audit logs, Failed to load AI gateway logs or Failed to load notification logs | That log table cannot load. Click Retry, or shorten the period. |
| Failed to load SSO login logs | The SSO login log cannot load. Click Retry, or shorten the period. |
| Failed to load socket logs | The socket log cannot load. Click Retry, or shorten the period. |
| Failed to load PII detection logs | The PII log cannot load. Click Retry, or shorten the period. |
| Failed to load table DDL logs | The table DDL log cannot load. Click Retry, or shorten the period. |
| Content not logged | The user switched off DataMind Oda content logging, so the request and response bodies were not recorded; token usage and costs still were. Hover over the badge to read the reason. |
| [REDACTED] | A value the platform must not keep readable, such as a password- or token-like body field or a sensitive header, was replaced before storage. Nothing to do; look for the value in the system that owns it, not in the log. |
| No message, No query params, No route params, No request body or No response body | That section of the details has nothing recorded for this row. Read the other sections and the status for context. |
| Not recorded | The Authorization request or ID token claims section has nothing stored for this attempt. Read the Error and IdP fields for context. |
| Request was aborted | The request was cut short before it finished, so expect partial output. Check who stopped it. |
| Shortened for storage - original size | The stored payload was cut because it was too large; the notice names the original size. Treat the payload as incomplete; the ids and settings around it are intact. |
| Failed to load notifications for this period | A workflow alert's notification history failed to load. Widen the period, then try again. |
| No notifications in this period | A workflow alert sent no notifications in the period. Widen the period. |
| Couldn't load statements, or Failed to load run details when no reason came back | A table DDL record's statements did not load. Close the record and open it again. |
| Run error | The run failed; the text under the title is the error the run recorded. Read it, then read the failed statements below for their own reasons. |
| Recreation reasons | The platform recorded reasons why the table was recreated, listed under the title. Read them to understand why the table was rebuilt. |
| Statement error | That statement failed; the text under the title is its error. Read the SQL above it and the run's Run error notice for context. |
| Loading statements… | The run's statements are being fetched. Wait; the notices and the statements appear when the fetch finishes. |
| No statements were recorded for this run. | The run's record holds no statements to show. Read Recreation reasons and Schema changes, if present; there are no statement rows to expand. |
| No SQL was recorded for this statement. | The statement ran without a recorded SQL text. Use the statement's channel and duration, and the run's Schema changes, to place it. |
| Could not load data | A Mind Analytics card cannot load. Change the period or refresh. |
| No data for this period. | Nothing happened in the period. Widen the period. |
| No insights for this period | There is nothing to show for the period. Widen it. |
| No items found. | The side-list search matches no Mind, user or role. Clear or change the search text. |
| No active members in this period. | The selected role had no active members in the period. Widen the period, or pick another role. |
| No results, with Try a different search term. | The search finds nothing. Change the search. |
The platform's own area has its own pages: Platform services and Platform container logs; updates are described in Platform updates and the Installer card.
| You see | What it means and what to do |
|---|---|
| Not available on this installation: DataMind manages its services and updates. | Your installation is managed by DataMind, so services and updates are handled for you and the Platform area offers only logs. Nothing to do here. |
| No control plane behind the gateway | This installation has no control plane behind the gateway, so the services, updates and logs screens cannot work here. Nothing is broken for you; this installation runs without the platform controls. |
| Control plane can't reach its backend | The control plane runs, but the part behind this screen does not answer. Click Retry; if it repeats, ask your administrator to check the installation. |
| Control plane not reachable | The control plane did not answer at all. Click Retry; if it repeats, check your connection and ask your administrator. |
| Restart started or Stop started | The request was accepted and a maintenance job started; the service name shows under the title. Watch the job in the Jobs list; the row usually moves to Starting straight away, or to Down once a stop completes. |
| Could not start the restart or Could not start the stop | The action was refused or did not start; the reason follows. It may name a missing Restart Platform Services or Stop Platform Services permission, a job that is already running, or a service your role cannot touch. |
| Access denied. You do not have permission to execute the service name | A restart was refused. Restarting needs Restart Platform Services; ask an administrator for it. |
| Access denied. You do not have permission to delete the service name | A stop was refused. Stopping needs Stop Platform Services; ask an administrator for it. |
| Deployment service rejected the request | The platform refused the action. Read the reason, refresh the panel and try again. |
| Deployment job not found | The job you were following has left the list; jobs are kept for an hour. Start the action again if you still need it. |
| A deployment job is already running | The installation handles one maintenance job at a time. Wait for it to finish, then try again. |
| Deployment service is unavailable | The service behind platform actions cannot be reached. Try again in a moment; if it stays, ask your administrator. |
| Service groups unavailable: reason | The definition that groups the services could not load. Click Retry; if it repeats, read the reason. |
| Service schema unavailable - groups are approximate | The group definition could not be read, so every service is shown in one group; the states still come from the running installation. Click Refresh to try again. |
| Deployment files incomplete on the host | The installation's deployment files are incomplete, so some services may be missing from the panel. The list still shows what is running; ask your administrator to check the host's deployment files. |
| Only completed init containers here - toggle "Show completed init" to see them. | Every service in this group is a finished one-shot setup service, hidden by the Show completed init switch. Turn it on in the strip to show them. |
| Loading platform services or Loading jobs | The services panel or the jobs list is loading its first snapshot. Wait for it to finish. |
| No jobs yet. | No maintenance job has run yet, or every job is older than the one-hour retention. Nothing to do; a restart, a stop or an update adds a job here. |
| Waiting for output… | The running job has not written any output yet. Wait; lines appear as the job writes them. |
| Reconnecting… | The job's live connection dropped and the page reconnects on its own. Nothing to do; the list still updates while the stream reconnects. |
| Access denied. You do not have permission to read logs for container | Your role cannot read that container's logs. For data-tier containers, ask for View Sensitive Container Logs. |
| No readable containers have logs in the selected window | The containers your role may read wrote nothing in the window. Widen the range, or clear the search. |
| Log store is unavailable | The log store cannot be read right now. Retry in a moment; if it stays, ask your administrator. |
| Download failed, with a reason | The export did not finish. Read the reason, then try again with a shorter window or a narrower search. |
| 10,000-line limit reached - narrow the range or click a bar in the chart above for older lines, or line limit reached in the footer | The view holds its maximum lines for scrolling, so older lines stop loading. Narrow the range or click a bar in the chart to reach further back; a download is not bound by this point. |
| Loading logs | The log list is loading its first page. Wait for it to finish. |
| No log lines in this window. | The selected window holds no lines. Widen the range or clear the search. |
| Waiting for new lines… | Live is on and no new line has arrived yet. Wait; new lines appear as the services write them. |
See Manage alerts.
| You see | What it means and what to do |
|---|---|
| Failed to load alerts, with a reason | The alert list cannot load. Click Retry. |
| Alert not found, with Back to alerts | The alert was deleted, or you cannot see it. Click Back to alerts. |
| Failed to load the alert, Failed to load the recipient roles or Failed to load the run history | Part of the alert's details failed to load. Open the alert again from the list. |
| Not run yet. | The alert has no runs yet. Nothing to do; run it with Run now to see a first row. |
| The role this alert runs as no longer exists. | The alert's Runs as role was deleted, so the alert cannot run. Open it with Edit and pick a role you hold in Runs as, then save. |
| Failed to pause the alert, Failed to resume the alert, Failed to run the alert or Failed to delete the alert, with a reason | The action did not complete. Read the reason and check that you hold the alert permissions you need. |
| The alert is already paused. or The alert is not paused. | The alert is already in that state, often because another tab changed it. Refresh the list. |
| Run failed: reason | Run now ran and the query failed. Fix the query or the role with Edit. |
| You can only run an alert as a role you hold, and you do not hold "role". | You picked a role you do not hold. Pick one of your roles in Runs as, or ask an administrator. |
| Triggered - email sent | Run now ran, the condition was met and recipients were emailed like a scheduled run. Nothing to do; the run and its email are in Recent runs. |
| Triggered - no email | The condition was met but no email went out, for example because every recipient is deactivated, no default email channel is set, or the notify mode sent nothing for a repeated result. Check Recipients and Notify, and that a default email channel is set under Admin > Notifications. |
| Condition not met - email sent | The run did not meet the condition and an email went out, for example a recovery email after the alert was triggered. Nothing to do; the alert is healthy again. |
| Condition not met - no email | The run did not meet the condition and nothing was sent. Nothing to do. |
| Alert paused or Alert resumed | The pause or resume succeeded. Nothing to do. |
| Alert deleted | The delete succeeded. Nothing to do. |
See Create an alert.
| You see | What it means and what to do |
|---|---|
| Validation Error, with a message about one field | A field is missing or invalid. Fix the field the message names. Cards marked Needs attention hold the problem. |
| Needs attention | A collapsed card hides a field that failed validation. Open the card and fix the message under the field. |
| Name is required or Keep the name under 255 characters | Enter a name, or shorten it. |
| Write the query the alert runs | Enter the SQL. |
| Pick the role the alert runs as | Choose a role in Runs as. |
| Use a 24-hour HH:mm time | Enter a time such as 09:00. |
| Pick a day from 1 to 31 | Choose a day of the month from 1 to 31. |
| Show between 1 and 100 rows | Enter a row limit from 1 to 100. |
| The email needs a subject | Enter a subject. |
| Pick at least one person or role, Pick at least one role or person or Pick at least one person or role to receive the alert. | Add a recipient, such as yourself or a role. |
| Every recipient role must be an active role., or a message that every recipient must be an active user | A picked person or role is deactivated or deleted. Remove it from Recipients and pick an active one. |
| Add at least one rule, or make the alert query based, before saving it. | Add a rule, or choose Query based and save again. |
| Pick a column, Enter a value or Enter the upper bound | Complete the rule. |
| Test failed, with a reason | The Test was refused or the query failed. Read the reason and fix it. |
| Changed since this test - run it again | You edited the alert after its last Test. Click Test again. |
| No rules yet. Add one to say when the alert should trigger. | A rule-based alert has no rules yet. Click Add rule. |
| No rules to evaluate | A rule-based alert has no rules to test. Add a rule. |
| Failed to create the alert or Failed to update the alert, with a reason | The save was refused. Read the reason, fix it and save again. The editor stays open. |
| You can only send alerts to yourself. Ask an administrator for "Notify Others With Alerts" to add others. | You hold only Create Alerts. Ask an administrator for Notify Others With Alerts to add other people or roles. |
| alerts cannot be created or changed while impersonating another user. | You are viewing as another user. Stop impersonating, then create or edit the alert. |
See Create an alert for the editor and its rules.
| You see | What it means and what to do |
|---|---|
| Rule N: column "name" is not in the query result. | The rule names a column the query no longer returns. Click Test and pick a listed column. |
| Rule N: column "name" has type type, which conditions cannot compare. | The column type cannot be compared. Cast the column to a number, date or text in the SQL. |
| Rule N: aggregate needs a numeric column, and "name" is type. | Sum and average need a number column. Pick a numeric column. |
| Rule N: "condition" does not apply to a type value. | The condition does not suit that column type. Pick another condition. |
| Rule N: "value" is not a valid type value. | The value does not fit the column type. Enter a value of the right kind. |
| Rule N: "value" is not a value of "column" (allowed values). | The value is not one the column holds. Choose one of the listed values. |
| Email column "name" is not in the query result. | An email column is no longer in the result. Click Test and pick the columns again. |
| An alert running as "role" may only read databases. The query reads tables. | The query reads tables outside the databases of the role. Change the query or the role. |
| The alert query failed: error | The SQL failed when it ran as the Runs as role. Open the query in the Editor with the same role, fix it and test again. |
| file was not attached: it is N MB, over the 19.0 MB email limit. | The attachment was too large, so it is missing from the email. Narrow the query or pick fewer columns. |
For the map itself, see Lineage and Explore and trace lineage.
| You see | What it means and what to do |
|---|---|
| Error, with the reason, or Failed to load lineage data. Please try again. when there is no reason | The map cannot load. Click the refresh button (tooltip Refresh lineage data). If it stays, reload the page. |
| Loading lineage data… | The map is drawing for the first time. Wait; the view and table buttons work again once it finishes. |
| Rearranging diagram… or Auto-reordering... | The map is re-laying out after a view or table-mode change, or still settling in the background. Wait; your selection is cleared while it rearranges. |
| Error, with Failed to load orphan nodes data. Please try again. | Orphan tables cannot load. Switch to Normal Tables, then try again. |
| Loading, with Orphan nodes data is still loading. Please wait a moment. | You chose All Tables or Orphans Only too early. Wait, then choose it again. |
| Unavailable, with Orphan nodes data is not available yet. | The orphan data did not arrive. Click the refresh button. |
| Lineage data refreshed successfully. | The refresh finished. No action is needed. |
| Export failed, with Could not find diagram to export. | You exported before the map rendered. Wait for the map, then export again. |
| Export successful, with Diagram exported as file | The PNG is saved. Find it in your downloads. |
| Edit not available, with Editing type tables is not yet supported. | That item type has no editor yet. Open the item from its own area instead. |
| Loading filters | The filter panel is still loading its values. Wait a moment. |
| No data sources match "search" or No source types match "search" | The Data sources or Source types search in the filter panel found nothing. Change or clear the search. |
| DataPrism is temporarily unavailable, so its models are not shown. | The models could not be read. Refresh later. |
| Only items you do not have access to use these tables. | Every Mind, model or deck in that lane is hidden from you. Ask for access to them. |
| Lineage preview unavailable. | The details panel has no small lineage preview for this item. Click Open in Focus under Related items instead. |
| No schema available, with Column metadata has not been loaded for this table yet. | The table's columns are not known yet, so the details panel cannot list them. |
| No columns match your search. | The column search in the details panel finds nothing. Clear or change the search. |
Messages from a table's popup in the Warehouse and the Lake, including the RLS step, the primary key banner and the Dependencies step. See The RLS editor: protection and modes, Build RLS access rules and Popup helpers: metric cards, banners and highlights.
| You see | What it means and what to do |
|---|---|
| When On, each permission group only sees rows matching its rules. When Off, every group can access all rows. | The Protection switch's hint in the RLS step. Set Protection to On to limit each group to the rows its rules allow, or to Off to let every group access all rows; the switch applies straight away. |
| Auto keeps SQL in sync with your rules. Manual lets you write SQL by hand - switching back to Auto discards manual edits. | The Editor mode hint in the RLS step. In Manual you edit the script by hand; copy your SQL elsewhere before switching back if you need it, because switching back keeps only the script generated from the rules. |
| Discard unsaved changes?, with You have unsaved RLS changes. Close without saving? | The expanded editor holds changes that differ from the step and you are closing it. Choose Discard to close and drop those changes, or return and save the step first to keep them. |
| No access rules yet, with Add a rule to control which rows each permission group is allowed to see. | The table's RLS step has no rule blocks yet, so no rule filters any group's rows. Click New Query to add a block; the button is unavailable while the editor is Manual or Protection is Off. |
| Visual rules unavailable, with Adding access rules is available only in Auto mode while you are editing SQL manually. | The editor is in Manual mode and no rule block exists yet, so the visual builder has nothing to show. Switch the editor back to Auto to build rules visually, or stay in the SQL view and edit the script by hand. |
| Primary key required. Define a primary key column before this view can be deployed. or the same message with this table | The item cannot deploy because no column is marked as the primary key, so the popup shows the banner instead of the deploy offer. Click Go to Columns, mark one column as the primary key, save and deploy. |
| No dependencies selected, with Choose tables your view depends on to give it the right upstream context. or the same sentence with transformation | The Dependencies step has no tables picked yet. Click Manage Dependencies and pick the tables the item depends on. |
Messages from the small query windows a popup opens: the version history, the data preview, the AI fix and the Editor hand-off. See Query history, Query data preview, AI query help: diff and fix and Open in Editor.
| You see | What it means and what to do |
|---|---|
| Cannot fix query, with Save general settings first, then try Fix with AI again. or Save the dictionary first, then try Fix with AI again. | The item you are fixing is not saved yet, so the repair cannot run. Save it first, then try Fix with AI again. |
| Fix with AI failed | The repair request did not finish, or no corrected query came back; the reason follows the title (the fallback reads Failed to generate a fixed query). Try again or fix the query by hand; the window stays open for a retry. |
| Loading history... | The saved versions are still loading, so the list is not ready to pick from yet. Wait; the list fills when the versions arrive. |
| No query history yet | The query has no saved versions to show. Nothing to do; versions appear here as the query is saved with changes. |
| Select a version to preview its query | The detail pane has no version to show; the list is still loading, or the query has no saved versions. Wait for the list, or pick a version in the Versions list once it shows one. |
| No data preview available, with There is no query result to display yet. Run the query to see its data here. | The Query Data Preview window has no result to show yet. Run the query from the editor that opened the window; the rows replace the empty state when the run returns. |
| No data available, with This query executed successfully but did not return any rows. | The query ran and returned no rows; the run itself succeeded. Change the query if you expected rows, then run it again. |
| Console created, with Created "name" | Open in Editor created a console for the query you sent, and it is selected. Nothing to do; the console is ready and holds your SQL. |
Messages from the shared run log table and the diagnostics windows behind a failed or warned run. See Sync Log tables and Error stacks and runner diagnostics.
| You see | What it means and what to do |
|---|---|
| UTF-8 replaced: n, or a warning count such as 1 warning or 3 warnings | The loader's warning badge on a finished load; it replaced invalid UTF-8 sequences so the run could finish. Open the row's report to read the exact sentence and the affected records. |
| Load failed | The load attempt failed. Read the report's Page, HTTP, Decode and Warnings details; for the load's own messages, see Lake troubleshooting. |
| Load finished with warnings | The load completed and kept warnings; the data was loaded. Read the warnings and the affected records to know what changed. |
| ... more records not listed | The report lists only part of the affected records, so the count in its sentence is a lower bound. Treat it as such. |
| [hidden: no data access] | The affected record keys are hidden because you may not read the table's data. Ask a colleague who can read the table if you need the values. |
| Abort run | The stop control on a run's row; some areas name it for their runs, such as Abort test run and Abort transformation run in the Warehouse, or Abort synchronization in the Lake. Use it on a row that has not finished; while the request is in flight the control turns into a spinner and cannot be clicked again. |
| Delete log entry | Removes a finished run's row from the log; a row the area cannot delete shows no control at all. Use it on a row that is not running; it is disabled while the delete is in flight. |
Read the reason in the bar, then click Retry. If your search term caused the failure, change the term. The search box stays on screen, so you can edit it.
A custom period is limited to one year. Choose a shorter custom range, or use a preset such as Last 30d.
Several exports were running at once. Wait a moment, then start the export again.
The SQL failed when it ran as the role in Runs as. Open the query in the Editor with the same role, fix it, and test the alert again. See Create an alert.
You picked a role in Runs as that you do not hold. Pick one of your roles, or ask an administrator to give you the role you need.
Check its status first: a Paused alert does not run until you resume it. If the alert refuses to run with The role this alert runs as no longer exists., its Runs as role was deleted. Open it with Edit and pick a role you hold.
A field is missing or invalid, and the message names it. Open the cards marked Needs attention, fix the field and save again.
The file was over 19.0 MB, so it was left out. The email says so. Narrow the query or select fewer columns, then test the alert again.
Click the refresh button first. If Failed to load lineage data. Please try again. stays on screen, reload the page.