-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Connecting to core is a temporary startup state. Wait briefly for the desktop
application to finish loading.
Core unavailable means the workspace could not reach the desktop core. A
browser preview always shows this state because it does not include the desktop
runtime.
Close DRAFT and open the desktop application again. If the message repeats, record the DRAFT version and operating-system version when reporting the issue.
Core status invalid means DRAFT rejected an unexpected status response or
update. Restart DRAFT. If the message returns, report the DRAFT version and the
exact visible message.
DRAFT received an unsupported application version. means the interface and
desktop core do not agree on the application version.
Install one complete DRAFT build rather than combining files from different builds. Restart the application after installation. If the message remains, report the build source and version.
DRAFT could not deliver the core status event. means startup validation ran,
but the status update did not reach the workspace.
Restart DRAFT. If the failure repeats, report the DRAFT version and exact message. Do not treat the workspace as connected while this message is shown.
DRAFT could not read the core status. is the fallback for an unknown desktop
status failure.
Restart DRAFT and report the DRAFT version and exact message if it repeats.
The current interface does not save documents. Reloading the workspace or closing DRAFT discards edits. There is no recovery path for a discarded pre-release editor session. Keep important work in another saved document.