> ## Documentation Index
> Fetch the complete documentation index at: https://docs.generalvalidation.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting and logs

> Match what you see in General Validation to the next action, find the Spark job and Results folder in Fabric, and know what to send support.

Start with the affected page in General Validation. Note the error code and
request ID when the app shows them, and the Run ID for anything about a Run.
General Validation records configuration, status, and Result summaries. Spark
execution, exact values, and mismatch evidence stay in your Fabric tenant, so
some symptoms are resolved in Fabric rather than in the app.

## What you see and what to do

| What you see | What to do |
| - | - |
| Sign-in returns you to the sign-in page, or the app shows "Sign in again to continue." | Sign in again with the same Microsoft work account. If Microsoft asks you to complete your organization's sign-in policy, finish it and you return to the page you requested. If the page says Microsoft sign-in could not be completed, click **Return to sign in** and try again. If you signed in with the wrong account, click **Use another Microsoft account**. If the app says your directory is already connected to an organization, ask one of its Owners to invite your work email, then sign in and click **Accept invitation**. See [Sign-in and team access](https://docs.generalvalidation.com/administration/access.md). |
| Sign-in shows "Your organization needs to approve General Validation". | Your tenant requires an administrator to approve new applications. Click **Copy** next to Approval link for your administrator and send the link to a Microsoft Entra administrator. The administrator signs in with their own account and approves the application for everyone in your organization; one approval covers every permission General Validation requests. After they approve, sign in again. If the page says an administrator declined the request, send the same link again and ask them to review it. |
| Fabric capacity on Environment lists nothing, or shows "No available Fabric capacity found." | Only active F, P, and FT capacities visible to the signed-in Owner are listed. Ask your Fabric administrator for permission to assign workspaces to an active capacity, then click **Refresh**. General Validation uses your existing capacity; it does not purchase or resize capacity. |
| A setup step shows Needs attention, or the page was reloaded during setup. | Click **Retry setup**. Setup resumes from the resources already created and does not create duplicates. If the alert says Microsoft denied setup access, ask your Fabric administrator to allow workspace creation and capacity assignment for the Owner running setup. If it says setup already started on another capacity, select that capacity. If it reports duplicate General Validation workspaces, Results Lakehouses, or validation jobs, resolve the duplicates in Fabric, then retry. If it says Fabric could not complete setup, open the workspace in Fabric to inspect the failed operation. See [Set up your Environment](https://docs.generalvalidation.com/get-started/environment.md). |
| Reinstall is required after a product update, or the validation job in your dedicated workspace was changed or deleted. | An Owner opens **Environment** and clicks **Reinstall**. Reinstall restores the validation job and keeps your Results; earlier Runs stay readable. Do this once before starting new Runs. If it fails, the card reads Reinstall needs attention; click **Retry reinstall**. |
| A workspace or Table is missing from Add Table Pair. | The workspace list shows only workspaces your signed-in Microsoft account can access, and it intentionally omits the dedicated General Validation workspace, which holds Results rather than validation Tables. Ask a Fabric workspace administrator for access, then click **Refresh source** or **Refresh target**. Table names include their schema, so look for the Table under its schema. Browsing a Warehouse needs Read on the Warehouse item and OneLake metadata access. If an amber alert asks you to connect, click **Connect Microsoft Fabric** or **Allow OneLake access** using the same account and directory as your General Validation sign-in. |
| A Test on a Warehouse Table shows Error with the reason Could not read the Tables. | Warehouse Tables are read through SQL with the permissions of the user who submitted the Run. That user needs Read on the Warehouse item and SQL SELECT on the Table; there is no fallback to storage when SQL access is denied. Grant the access in Fabric, then start a new Run. |
| A Run stays at Submitted or Running. | Click **Refresh Result**. Fabric queues and runs the job on your capacity; while the Run's page is open it refreshes on its own no more than once a minute, and you can leave and return later. If the page says Fabric may have started the Run, click **Refresh Result** first; if the job exists in Fabric, expand **Recover a submitted Run**, paste the job ID into Existing Fabric job ID, and click **Attach existing job**. This records the existing job and does not submit another Run. Click **View in Fabric** to inspect the job in Fabric monitoring. General Validation never resubmits a Run on its own; a new attempt is a new Run. |
| A Test shows Error with the reason Could not read the Tables, The Test could not finish, or Could not save Result details. | Could not read the Tables means the user who submitted the Run could not read a source or target Table; every Test in the Run reports it. Grant that user read access to both Tables in Fabric, then start a new Run. The Test could not finish means a mapped column is missing, the function does not support the column's type, or a value could not be cast; edit the Test or its column mapping and run again. Could not save Result details means mismatch evidence could not be written; confirm the user can write to the Results Lakehouse in the dedicated workspace, then run again. See [Runs, Results, and evidence](https://docs.generalvalidation.com/validate-data/runs-and-evidence.md). |
| View details shows an access error or "Could not load customer-side details." | Details are read by your browser directly from the Results Lakehouse with your own Microsoft identity, so you need access to the dedicated General Validation workspace in Fabric. Organization membership does not grant it; ask a Fabric workspace administrator to share the workspace. If the page asks you to allow OneLake access, click **Allow OneLake access**, then **Retry details**. If the artifact cannot be previewed, click **Open results Lakehouse in Fabric** and inspect the Run's folder there. |
| "Table Pair limit reached" | Your plan's active Table Pair limit has been reached. Delete a Table Pair you no longer need, which archives it and keeps its Runs and Results, or ask an Owner to change the plan in Billing. See [fabric.pair\_limit\_reached](https://docs.generalvalidation.com/errors/fabric.pair_limit_reached). |
| "Active entitlement required" | An active trial or paid plan is required to create Table Pairs and start Runs. An Owner starts or renews a plan in Billing. Existing Table Pairs, Tests, Runs, and Results remain readable, and Runs already started still finish. See [fabric.entitlement\_required](https://docs.generalvalidation.com/errors/fabric.entitlement_required). |
| A Table Pair or Test shows Not run after an edit. | Its join keys, filters, or Tests changed since the last Run, so the previous Result no longer describes it. Past Runs and their Results are unchanged. Click **Run validation** to get a Result for the current definition. |

## Fabric monitoring

Your browser submits each Run as a job of the Spark Job Definition named
General Validation executor in your dedicated workspace. Click **View in
Fabric on Environment** or on a Run to open that workspace. Fabric's
monitoring for the workspace lists each job with its status and Spark logs and
diagnostics; those stay in Fabric, and General Validation records only a fixed
reason for a failed submission or job, never Fabric's message.

A Run whose Tests fail also shows as failed in Fabric monitoring. Open the Run
in General Validation to see whether a Test failed or the execution itself had
a problem. If the Run's page says "No results were saved for this Run.", open
the job in Fabric to see why.

Each Run writes its summary, a details file with exact values, and Parquet
mismatch evidence to the GeneralValidationResults Lakehouse under
`Files/GeneralValidation/results`, in a folder named with the Run ID. The
Run's page shows the first eight characters of the Run ID; the full ID is in
the page address. Each Run also keeps the exact instructions it executed, which
you can review in the Run's folder and in Fabric's Spark monitoring. Previews
in the app show at most 100 mismatched rows; query the Parquet files with a
notebook or SQL endpoint in Fabric for the complete evidence. You own these
files and control their retention. General Validation never deletes them;
Remove on Environment deletes the whole dedicated workspace, including
this Lakehouse.

## Request IDs and support

When a General Validation API call fails, the app shows the error code and a
request ID with the message. Send these to
[support@generalvalidation.com](mailto:support@generalvalidation.com):

* the error code and the request ID, or the Run ID for anything about a Run;
* the time it happened, in UTC;
* the page you were on and what you clicked.

Failures during setup, browsing workspaces and Tables, Run submission, status
checks, and evidence previews have no request ID, because those calls go from
your browser straight to Microsoft. For those, send the Run ID where there is
one and what Fabric monitoring shows for the job.

Keep rows, exact values, credentials, tokens, and evidence files in your
tenant. Do not attach them, and review screenshots so they do not include
them. Support does not need them: General Validation's operational logs hold
request IDs, operation states, error codes, and a fixed set of diagnostic
metadata, and never tokens, credentials, request or response bodies, filter
values, exact values, or rows. Those logs are retained for 30 days.

The [Error codes](https://docs.generalvalidation.com/administration/errors.md) reference lists every code the app can show with
its next step.

## Browser diagnostics

General Validation writes fixed-field diagnostic records to your browser's
developer console for sign-in, API calls, and page rendering. Each record
holds the action, its outcome and status, the error code, and the request ID.
Records never contain tokens, headers, request or response bodies, query
strings, account or directory identifiers, page text, full addresses, or error
messages and stack traces. They stay in your browser and are not sent to
General Validation. Review a record before sharing it; after review it is safe
to include in a support message.

Requests your browser makes directly to Fabric and OneLake, for Environment
setup, browsing, Run submission, status checks, summary import, and evidence
previews, produce no console record and no General Validation log. Use Fabric
monitoring for those.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.