Use this guide when Bridgit cannot connect, voice input does not work, a file cannot be attached or an answer does not match the report you intended. Start by identifying the affected workflow so you can check the relevant settings and context.
Identify the Affected Area
- General Chat, Query Building, Finished Reports Viewer or Visualize Viewer.
- A typed request, a live voice discussion or dictation.
- A connection problem, query error, unexpected answer or attachment problem.
- For Designer authoring, confirm that your VDM version includes the relevant Bridgit integration.
Bridgit Does Not Respond or Reports a Connection Error
- Record the exact error and when it occurred.
- Confirm that Bridgit has an approved API key and that the intended model is available to that account.
- Check the relevant VDM settings category: User Options, Global Options or Service Options. Changing one category does not mean the others have changed.
- Follow any restart prompt shown after a settings change.
- Ask IT to confirm outbound HTTPS access to
api.openai.comover TCP port 443, including any proxy or inspection requirements.
If an error identifies authentication, billing, a model or a usage limit, have the OpenAI account administrator review that account. Do not share the API key in a screenshot or support request.
The Microphone Works Differently Than Expected
| What you see | What to check |
|---|---|
| Speech is inserted into the message field | The chat may be using dictation. Enable Talk to Bridgit when you intend to have a live discussion. |
| No speech is detected | Check the selected microphone and Windows microphone access. End and restart the voice discussion after correcting the device or permission. |
| Bridgit responds before you finish speaking | Review Voice Activity Detection and Voice Turn Eagerness with an administrator. Mic Sensitivity applies to server_vad. |
| You cannot hear the reply | Check the output device, volume and headset. Continue by typing while resolving the audio issue. |
Bridgit Is Discussing the Wrong Report
- Confirm the active connection and the query or viewer you intended to discuss.
- Review the chat’s Focus selection when it is available.
- State the intended report or current change explicitly.
- If an earlier task is no longer relevant, use New chat from the + menu when offered, then confirm the fresh conversation. The current report and query stay open.
After a report is refreshed or changed, an older answer is historical context rather than proof of the current result. Ask Bridgit to review the current report again when needed.
A File Cannot Be Attached
Check the file-upload controls for the chat you are using. Supported extensions and upload availability vary by surface. The general-chat upload list is not a promise that every embedded viewer or Query Building control accepts the same formats.
Confirm that the file is accessible, has the expected extension and contains only information approved for AI processing. Retain the exact upload error if the problem continues.
A Query Fails or Returns Unexpected Results
For execution errors, retain the SQL and database error. Confirm the active connection and any parameter values, then ask Bridgit to review the error in the same conversation.
For unexpected results, identify a specific missing field, incorrect filter, duplicated record or total. Compare the result with a known source. Ask an administrator to review Schema Vocabulary, Example Reports and Knowledge Health if a reporting definition or saved example is outdated.
Note: Validation can establish that SQL is compatible without establishing that the business interpretation is correct. Do not resolve a total mismatch by accepting an unexplained calculation.
A Request Is Taking Longer Than Expected
Check whether VDM shows a current working stage, queued request, error or completed result. Avoid repeatedly sending the same request while work is active. Where a Stop control is available, use it when you intend to cancel the current work. Designer background requests have additional recovery behavior; see Managing Long-Running Bridgit Designer Requests.
Information to Send to Support
- VDM version and the affected chat or Designer.
- The action immediately before the issue and whether it repeats.
- The exact error and an appropriate screenshot.
- Connection type and relevant model/voice settings, without credentials.
- Application Logs or copied Knowledge diagnostics when requested.
Review files, SQL and screenshots before sharing them. Include only the information needed to reproduce the problem.
Comments
0 comments
Please sign in to leave a comment.