# Troubleshooting cloud workspaces

Most web workspace failures fall into one of four layers: browser task, task/project binding, cloud machine readiness, or the command itself. Diagnose them in that order and preserve the existing project before creating replacements.

![Troubleshooting cloud workspaces in Foxora v5.0.3](/docs/images/v5.0.3/web-cloud/cloud-execution.webp)

## First checks

1. Confirm [app.foxora.ai](https://app.foxora.ai/) still shows the expected account.
2. Reopen the task from **foxora → Tasks**.
3. Confirm the intended project name in the header and **foxora → Projects**.
4. Switch the transcript to **Verbose** and capture the exact failed tool row.
5. Retry one read-only action, such as listing the project root or reading a known file.

Do not delete the project, clear browser data, or start multiple replacement tasks before this check.

## Match the symptom

| Symptom | Likely layer | Safe next action |
| --- | --- | --- |
| First file or terminal action is slow | Cold cloud-machine start | Wait for the current action, then retry one read-only operation once. |
| Workspace or terminal reports unavailable | Cloud readiness or expired browser task | Refresh after preserving unsent text, sign in again if prompted, and reopen the same task. |
| Files appear in the transcript but not the Files tree | Wrong active project or stale view | Check the project header, reopen the project, then refresh the Files view. |
| Export says there is nothing to download | Task has no output in the selected project | Verify the task’s generated scratch project and ask Foxora to name the exact file path. |
| Command remains running | Interactive prompt or long process | Inspect the command, interrupt it if safe, then rerun with non-interactive flags or a bounded timeout. |
| A recreated project lacks dependencies | Derived folders were intentionally excluded from backup | Reinstall from the lockfile and rerun the build. |
| Artifact preview fails | Renderer or invalid artifact source | Switch to **Code**, download the source, and inspect the error before regenerating. |

## Recover without losing evidence

1. Copy the exact error, task name, project name, and approximate time.
2. Download any still-accessible artifact or project archive.
3. Ask Foxora to summarize completed steps and unresolved work in the current task.
4. Retry the smallest failing operation.
5. Create a new task only if the existing task cannot reconnect, and attach the existing project rather than generating another empty one.

If the same read-only operation fails after a refresh and reauthentication, report the browser, Foxora web version, task identifier, project name, failed tool, and timestamp. Do not include access tokens, provider identifiers, private environment variables, or unrelated project files.