Skip to help
ScopedHelp CenterContact supportSign in

Troubleshoot desktop startup

Find the next step for database connection, migration, application, and session errors in Scoped for desktop.

Scoped desktop; check platform availabilityReviewed

Before you start

Keep local files, saved configuration, and any external database intact. Do not delete a database or application-data folder to clear a startup error. Follow the steps for your installed version and storage type.

Connection and database errors

For local storage, retry opening Scoped and check free disk space. If the storage runtime is missing, reinstall the app while preserving its data folder. Open Advanced storage only if you intentionally use an external database.

External database errors

For DATABASE_UNAVAILABLE or DATABASE_AUTH_FAILED, ask the database operator to check the connection. For EXTENSIONS_MISSING, review the external database requirements. Never send credentials to support.

Backup and migration errors

If a backup or update check fails, resolve the reported disk or file problem before retrying. An incompatible schema requires a matching app version; installing an older app does not downgrade your data.

Review available recovery options in Data. The standalone recovery flow protects the current workspace and validates a separate copy before switching. External-database recovery belongs with its operator. A portable export omits authentication credentials and agent permissions; agents need to reconnect after restore.

Application and session errors

If you enabled a local password, use the recovery code saved at setup to remove a forgotten password without deleting your work. Cloud password-reset emails do not reset a standalone local password or repair an external database connection.

Retry startup after resolving the reported issue. Preserve database and application files when reinstalling.

Contact support with diagnostics

Contact support with the error code, app version, and what happened. Optional diagnostics are previewable before you submit. The form accepts no files or support bundles. Never include passwords, full database URLs, access tokens, recovery codes, or workspace records.