Troubleshooting

When reporting a problem, include:

• the Resrch App version and release channel;
• your operating system and version;
• the action immediately before the failure;
• the complete visible error message;
• whether the problem happens again after restarting Resrch.

Startup or Core connection failure

1. Quit Resrch completely and start it once more.
2. Record the complete startup or core.session.hello error instead of only the final timeout line.
3. If the CLI is available, run resrch doctor and resrch paths.
4. Open the reported log_dir and preserve the relevant resrch.log.YYYY-MM-DD file. File logs exist only when file logging is enabled.

PDF or preview failure

• Confirm that the source file still exists and is readable.
• For a project, confirm that dependencies remain under the opened project root.
• Preserve the compiler diagnostic. A missing LaTeX compiler, a timeout, and a source compilation error are different failures.
• First Tectonic-backed LaTeX previews may take longer while support files are prepared.

Before sharing a log, inspect it for local paths, document titles, private source text, access tokens, and other credentials. Redact sensitive values without removing the actual error type. Use the support page for the available support channels.