Start with the visible error and the last action that worked. Preserve your task context and avoid creating duplicate work while the cause is unclear.

My hosted workspace is preparing or reconnecting

Wait for the lifecycle screen to resolve. Use its retry option when offered. After reconnecting, inspect the existing chat or run before launching another copy. If it stays unavailable, record the visible message and approximate time for support without including secrets.

An app cannot access my account

Check Apps for the connection and its status. For manual setup, check the credential name and category in Connections. Confirm the external account still permits access. A stored secret can be expired or insufficient for the requested action.

Gideon cannot find a file

A path on your laptop is not automatically available to a hosted runtime. Upload the file, use an accessible source, or identify the file in the remote workspace. For Knowledge, check ingestion and try an exact title or phrase.

Voice is silent or unavailable

Check browser microphone permission, your input and output devices, and whether the feature is available in the current runtime. Use text chat to keep working. Hosted customers do not configure model provider keys to fix voice.

A run is waiting

Read the pending approval, gate, or missing-input request. Resolve it and check progress. Do not treat waiting as failed or completed. For a stopped run, review its output before restarting.

A schedule produced no notification

Check run history and its result first, then delivery destination, silent behavior, quiet hours, and notification preferences.

I run Gideon myself

Use gideon doctor and check the gateway is running on the expected port. Source changes in the Python runtime need a restart. See self-hosting for installation-specific guidance.

When something gets stuck