Skip to Content
Browse documentation

Troubleshoot CodeSpace and Recover Pending Edits

Preserve unsaved text before resolving CodeSpace loading, search, file-access, size, encoding and save-conflict failures.

Protect pending work before troubleshooting. CodeSpace has no autosave, persistent drafts, version history or guaranteed browser-close prompt. Copy unsaved text privately before a reload, session change or stale-tab closure.

Common symptoms

SymptomChecks and next action
Workspace remains empty or fails to initializeMonaco assets, browser errors, UAPP session and file-service availability. Ask the provider to inspect persistent failures.
File missing from ExplorerExplorer filters out files not marked editable; inspect the full directory in File Studio.
File will not openConfirm existence, account ownership, regular-file status, protected-path policy, UTF-8 content and edit-size limit.
Save unavailableSelect a file and make an intended edit; Save applies to an active modified file.
Unable to save filePreserve text; check file-service response, account ownership, disk space, edit-size limit, demo status and external-change conflict.
Save All partially succeedsInspect counts and remaining modified tabs; successful files are already changed on disk.
Refresh shows old editor contentExplorer Refresh reloads the tree only; an already-open tab retains its model.
Quick Open stops respondingPreserve pending work and use Explorer. A failed request can leave no useful visible error.
Format unavailableThe active language may have no bundled formatter; check Output and avoid repeated blind submissions.
Problems panel is emptyLanguage support and open-model scope limit diagnostics; run actual application checks separately.

Recover a disk-change conflict

If another editor, deployment or application changed a file after it was opened, the timestamp check can reject saving. Protect both versions: preserve pending text, inspect/download the latest disk file through File Studio, merge deliberately, then close and reopen the stale editor tab before applying the merged text. Saving explains the workflow and in-flight-save caveat.

Inspect errors safely

Some errors appear in Output or the creation dialog; others appear only in browser Console/Network responses. Record the operation, approximate time, account-relative path and sanitized error text for the provider. Do not share file contents, session cookies, credentials, request bodies containing code/secrets or private tokens.

If the file service is unavailable, the workspace can redirect to its unavailable-service page. Signing in again may resolve an expired session, but first preserve pending text. After an uncertain response, inspect disk state before retrying: one-file replacement may already have happened even if the browser did not receive success.

For transfers, permission repair and Trash, use File Studio. Do not use broad permission changes as a general remedy for editor problems. No live file operation is needed just to collect a display or loading error.