Maintaining Bridgit Knowledge and Resolving Health Warnings

The Knowledge Editor’s Health tab helps administrators identify missing schema information, retrieval-index problems, stale Successful Queries and invalid relationships. Use the action that matches the warning; an index refresh and query validation perform different work.

Trouble Viewing Images? Right-click an image and select Open in new tab to view a larger version. You can also zoom in using Ctrl + Mouse Wheel.

Open Knowledge Health

1. In Tables and Fields, right-click the required Connection Profile.
2. Select Edit Knowledge (Beta).
3. Open Health.
4. Select Refresh Health and review the listed issues.

Choose the Appropriate Action

Note: Refreshing schema can query database metadata. Index rebuilding may send Knowledge text to OpenAI for embeddings. Revalidation can contact the database for compatibility checks. Review the connection and configuration before confirming an operation.

Resolve Missing Schema or Retrieval Information

1. If Discovery SQL is missing, have an administrator enter and save the appropriate metadata query in Schema Discovery.
2. Select Refresh Schema and review its result.
3. If embeddings or retrieval entries are missing or stale, select Refresh Retrieval Index.
4. When the operation finishes, return to Health and select Refresh Health.

Do not use an index refresh as a substitute for correcting an invalid table, field, join or saved query.

Revalidate Stale Successful Queries

1. Confirm that the stored schema catalog has been refreshed.
2. Review the stale-query issues in Health.
3. Select Revalidate All Stale, or select an individual issue and use the available Revalidate Selected action.
4. Review the confirmation and continue when appropriate.
5. Read the results before restoring or reusing a query.

A query that passes the supported full result-shape check can receive an updated schema fingerprint. A query that definitively fails can be disabled, with the reason recorded. A query that cannot be safely validated remains unchanged and may require normal execution for verification.

Select Cancel Revalidation to stop the batch after the current validation item. Unprocessed queries remain unchanged. Successful compatibility validation does not verify business totals or reporting meaning.

Quarantine or Restore an Item

Use Quarantine All Invalid to disable the invalid join rules currently identified as actionable. The rules remain stored with their reason and validation context; this is not a general delete operation.

Select an individual Health issue to see the action appropriate to that item. Depending on its state, the action can open the editor, quarantine it, revalidate it or offer Restore Selected. A join rule must pass the applicable compatibility checks before it can be restored. Review a disabled query’s definition before allowing it to be reused.

Verify the Result

1. Refresh Health again and check which warnings remain.
2. Test a representative Ask Bridgit request using the same connection.
3. Review a generated or retrieved query and verify its results against an approved source.

If a Warning Persists

Select Copy Diagnostics and contact BridgeWorks Support. Include the VDM version, connection type, affected Knowledge area, action performed and exact error. Review copied diagnostics before sharing them and omit credentials or sensitive query values.

Related Articles

• Teaching Bridgit About Your Database
• Finding and Reusing Reports with Bridgit
• Bridgit AI Knowledge Editor Overview
• Bridgit AI Data Privacy: How Your Data and Knowledge Are Handled