Finished Reports and Visualize design requests can take time to prepare, render and review. This guide explains the working states, queued follow-ups and controls available in VDM versions that include Bridgit’s Designer background-request workflow.
Read the Current State
| What VDM shows | What it means | What to do |
|---|---|---|
| Working or a named design/review stage | The current request is being processed. Different stages can include gathering context, generating a design and reviewing a rendered result. | Wait for the result or use Stop if you intend to cancel. |
| Queued or a pending follow-up count | A later request has been retained while earlier work finishes. | Let the earlier request finish; do not resend the queued request. |
| Elapsed for this step | Time spent on the current step, not the entire conversation. | Use it as progress context, not a completion estimate. |
| A completed/applied result | The relevant request finished and VDM reports its outcome. | Inspect the report or dashboard and verify the requested result. |
| An error, recovery message or uncertain outcome | The request needs the action described by the message. | Read the message before submitting another request. |
A working indicator is not a promise of a completion time. A queued acknowledgment is not a finished design.
Send a Follow-Up While Work Is Running
You can provide another design instruction while the current request is active. VDM retains supported follow-ups in order and applies each against the native report state available when that request begins.
A queued instruction is not merged into a model response that is already being generated. If you submit the same instruction twice, those can be treated as two separate requests. Review the pending count and avoid duplicate submissions.
Note: The follow-up queue is held in memory and is not retained across application termination. Recovery of an accepted background job is separate from retaining every queued follow-up.
Switching Between Designers
Finished Reports Designer and Visualize Designer share the Bridgit conversation surface. Only one Designer job can own it at a time. If another Designer is busy, wait for its work to finish or stop that request before switching.
Temporarily hiding or detaching the chat does not mean that a queued edit has completed. Return to the same Designer context and review its state before continuing.
Stop, Undo and New Chat
| Action | Use it when |
|---|---|
| Stop | You intend to cancel the current work. Wait for the cancellation outcome before sending a replacement request. |
| Undo | You want to reverse an applicable completed Bridgit change. VDM checks whether later changes make restoration unsafe. |
| New chat | You want a fresh conversation while keeping the current content and query open. Use the + menu and confirm when prompted. |
Stopping work does not undo an earlier completed change. New chat is not an undo operation and should not be used merely because an active request is taking longer than expected.
Recover After a Connection Problem
VDM can retain information about an accepted Designer background job and check that job before submitting new work in the same chat. Keep the original chat, provider account and model context when following the recovery message.
If VDM cannot determine whether a submission was accepted, it can block an automatic duplicate submission. Read the message and contact support if necessary. Starting a new chat permits a fresh attempt; it should be an intentional choice, not an automatic retry strategy.
If a response has expired or a reference file is no longer available, follow the error and attach the original reference again when requested. Do not assume that a locally retained filename is the file itself.
Voice During Designer Work
You can ask about progress or request spoken working updates during a supported Talk to Bridgit discussion. Working announcements and final results are different: a spoken acknowledgment confirms receipt or queueing, while completion must reflect the actual Designer outcome.
If you prefer quiet while work continues, tell Bridgit. Ending the microphone discussion stops the voice interaction; use the work-cancellation control when you also intend to cancel the Designer request.
Verify Before Continuing
After completion or recovery, inspect the actual report or dashboard. Check the requested controls, filters, calculations and exports. If the outcome is uncertain, preserve the current View and the exact message before asking for another design change.
If You Need Support
Provide the VDM version, affected Designer, request time, visible stage and exact error. Include the relevant logs when requested. Do not include API keys or reference material that your organization has not approved for sharing.
Comments
0 comments
Please sign in to leave a comment.