Skip to main content
Start with the narrowest boundary that can explain the symptom:
  1. Correct organization and channel.
  2. Correct host, URL, app, file, tenant, or phone.
  3. Current activity or pending approval.
  4. Effective tool policy and credential readiness.
  5. Local helper and OS permission.
  6. VPN, proxy, firewall, external service, or usage limit.
Open the activity stack and status bar before retrying. Repeated retries can duplicate external writes, payments, calls, or background work.

Sign-in and scope

Channels and policy

Terminal, RDP, and host access

Copilot

Browser and Computer Use

Connectors and MCP

Dashboards and apps

Files and organization memory

Org Brain

See Org Brain for supported sources and activation controls, and Memories and search for personal memory.

Digital workers and approvals

See Digital workers for states, triggers, human gates, and recovery.

Managed Remote Desktop

Managed endpoints use a separate enrollment, access, consent, and session flow from the RDP host protocol. Check Managed Remote Desktop for deployment and platform availability when the symptom concerns an enrolled endpoint, an access request, consent, or session control. Use the host-access checks above for a direct RDP connection.

Calls and Audio Use

Usage and billing

Firmware staging

Studio Remote

Collect support evidence

Include:
  • Studio version and operating system.
  • Organization ID and channel name, without private content.
  • Time and time zone.
  • Exact surface, target type, and expected result.
  • Activity and status state.
  • Redacted log excerpt and reproducible steps.
Remove tokens, passwords, private keys, session cookies, sensitive customer data, and complete credential-bearing URLs before sharing logs or screenshots.

System requirements

Review supported platforms, network paths, permissions, and feature-specific needs.

Settings

Review workspace, profile, AI, permissions, calls, firmware, Billing, and Key Chain.