Desktop troubleshooting

Start with the part of Desktop that failed: opening the application, loading a project, running code, displaying a figure, or synchronizing cloud files.

First checks

1. Select the run or file that shows the problem.
2. Read the first error and open its source location.
3. Confirm the active project and execution target.
4. Reproduce the problem with the smallest relevant file or command.
5. Save the error details and logs before clearing data or resetting settings.

For a support report, include the Desktop and Runtime versions, operating system, project type, execution target, minimal reproduction, and complete first error.

Desktop does not open

Restart the application and record the stage shown on the startup screen. A startup error may identify project loading, storage access, Runtime initialization, or an update.

If an update repeats or fails, record the installed version and update channel. Check system time, available disk space, and network access to the configured release service.

A local project does not open

Use Open folder and select the directory again. This restores access when the folder moved or the operating system permission expired.

For a save conflict, keep the unsaved editor buffer open and compare it with the file on disk. Choose the version you want before continuing to edit or run the file.

A cloud project does not open or update

Confirm that you are signed in, using the intended organization, and still have project access. Reconnect the project after restoring network access.

When one file appears stale, compare its cloud history with the unsaved editor buffer. Preserve local edits before refreshing or replacing project state.

See Server troubleshooting for authentication, organization, storage, and synchronization problems affecting multiple clients.

Code does not run

Try a scalar expression in the Command Window:

1 + 1

Then run a small array operation before returning to the full source. This separates Runtime startup from a problem specific to the program or workload.

For a failed run, select it and start with the first structured diagnostic. See Errors and diagnostics for compilation and Runtime errors.

GPU execution fails

Disable GPU acceleration and run the same source on CPU. If CPU execution succeeds, record the GPU adapter, operation, input shapes and types, and Runtime error.

Reduce the input size for a minimal reproduction. Check that the operation supports acceleration and that the selected adapter has enough memory.

Variables or figures are missing

Confirm that the intended run is selected. Review Output for an error before the variable assignment or plotting call.

For an earlier run, check whether run persistence was enabled and whether its artifacts are still present. Rerun the source to recreate unavailable results. See Plots and variable inspection.

A notebook does not render or run

Open Markdown source mode and inspect the code fences around the affected cell. Preserve the file before correcting generated output references. Rerun the cell after the Markdown structure is valid.

When cells produce inconsistent results, restart the notebook workspace and run all cells from the beginning.