Diagnostics and recovery
Logs, crash reports, backups and securely send data to support.
If the program does not start
- Check free space, data directory permissions, and Windows messages at startup.
- Open the dependencies page and recheck the components required by the selected feature.
- Save the error text and the time of the failure, then find the corresponding log.
- 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.
Please review the list of included files before submitting. Logs may contain paths, project names, service addresses, and work environment information, but project and autosave should not be added without separate selection.
Send to support
- Select the desired report and open the preliminary list of files.
- Remove or do not attach materials that cannot be transferred.
- After reviewing the archive, you can send it without registering or signing in.
Project restoration
- 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
- 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.