Diagnose the stage, not just the symptom
A Windsor task can stop during authorization, account selection, tool discovery, data retrieval, preview or execution. Those failures require different remedies. Begin with the connection card and the saved Work status before creating another connection or repeating a prompt.
Record the active workspace, installation label, connector/account, date range and visible error. Do not include OAuth codes, tokens, cookies or private provider payloads in a public support request.
Connection states and next steps
| What you see | Likely next action |
|---|---|
| Authorization needed / NEEDS_AUTH | Reconnect your own Windsor account through the secure provider flow. |
| Scope needed / NEEDS_SCOPE | Review the returned accounts and Save accounts and permissions. |
| Tool changed / TOOL_CHANGED | Refresh tools, inspect the new selection and reauthorize permissions as needed. |
| Paused or provider unavailable | Check the current provider/app state; ask an administrator rather than bypassing it. |
| Write disabled | Use a read-only request, or enable approved actions only where the installation supports them. |
Refreshing can intentionally disable writes and require scope review. That is not proof of a lost campaign or erased data.
No accounts or the wrong account
Add or repair the advertising/analytics source inside Windsor, then refresh its tools in TradeVulcan. Verify the connector and account identifier, not only the label. Multiple similarly named installations should be clearly named so the request stays on one connection.
An account not returned or not selected is outside that connection’s authorized scope. Asking for its number in chat does not grant access. If another tab changed the saved selection, reload and reconcile unsaved edits before saving.
Fields loaded, but no report appeared
Field metadata describes measures and dimensions; it is not the requested campaign data. Ask for a narrow data query with a selected connector/account and explicit dates. Work should use actual discovered fields rather than guess identifiers.
If a result is truncated, continue the supported pagination or reduce the period/dimensions. If the provider returns no rows, distinguish that from a timeout, insufficient permission or an unsupported field. Do not interpret a metadata preview as a complete campaign inventory.
Access changed during the task
A refresh, scope change, disconnect or provider schema change can invalidate earlier tool definitions and pending approvals. Reopen Connections and review the current state. After restoring access, ask for a fresh read before preparing changes again.
Do not paste credentials into the conversation as a shortcut. A successful reconnect should be verified with an ordinary scoped read; it is not blanket proof of write permission.
An external action has an unknown outcome
Use Refresh saved status and inspect the provider object. Do not click a new change merely because the prior operation lacks a final response. Keep the operation reference, requested values and target for support.
When reporting resumes, preserve the original period and definitions. A successful new report should not silently replace an earlier report’s dates or account just to obtain data.