Diagnostics and recovery

If the program does not start

1. Check free space, access to the data directory, and operating-system messages at startup.
2. If the settings window opens, check the required component on the dependencies page. If the application does not start at all, save the error text and use the available logs or the installed package’s maintenance tools.
3. Save the error text and the time of the failure, then find the corresponding log.
4. If the problem occurs after changing the settings, restore a known working configuration or backup.

Crash reports

After a failure, Screph saves a local report with technical details and associated logs. The report is not sent automatically.

Before sending, review the included files and check their contents for personal data and secrets. Logs may contain paths, project names, service addresses, and details of your working environment. Review the diagnostic archive separately from chat message attachments.

Send to support

Sending without registration does not hide information inside a log. A report may be associated with a connected account. If the result response is lost, check the submission status first: uploading a diagnostics archive again may create a second report.

1. In “Logging”, check the report source and the preview file list. If needed, export the archive locally to inspect it before sending.
2. If the archive contains materials you cannot share, do not send it. Instead, prepare a message describing the error with separately selected attachments that you can share.
3. After reviewing the archive, you can send it without registering or signing in.

Project restoration

Restore into a separate copy so that the original files remain available for comparison. If linked images or results are missing, look for them in the backup first; saving the project structure again will not restore lost materials.

• Use the last checked copy of the project or automatic save if available.
• Do not replace a damaged file with a single backup copy; first copy both files to a separate directory.
• Once opened, check the source images, markup, links, and attached results.
• For code projects, separately check for changes to the working folder in source control or a backup.

Problems with individual functions

When stopping a recording, processing run, or request, wait for the completion message. Cancellation may not immediately interrupt an external call already in progress, and stopping does not roll back saved files or input actions already sent. Check the result and target-window state before retrying.

• Computer Vision: check the selected model, dependencies and availability of the source image.
• Speech and LLM: check your connection profile, network, credentials, and the validity of the selected attachments.
• GUI Automation: check the script, target window, permissions and input method before running again.