Crash recovery

If Unreal Editor crashes or is killed, the plugin notices on the next launch, tells you what caused the crash, and picks up any Prophouse work that was interrupted. You do not need to do anything; this page explains what you will see.

Detecting a crash

While the editor runs, the plugin keeps a small record of what Prophouse is doing (idle, importing a job, processing a preview). A clean shutdown removes it. If the record is still there on the next launch, the previous session ended abnormally, and a couple of seconds after startup the plugin looks for Unreal’s crash report for that session in your project’s Saved/Crashes folder.

If there is no crash report (for example, the editor was ended from Task Manager or the machine lost power), the plugin writes a line to the Output Log and moves on without a notification.

The recovery notification

When a crash report exists, the plugin classifies it and shows one notification:

Cause	Message
Graphics driver, window manager or out-of-memory fault	`Prophouse: the last editor session was shut down by <cause> — not caused by Prophouse.`
A crash inside Prophouse code	`Prophouse: the last editor crash happened inside Prophouse code …` It names the asset being processed if there was one, and asks you to share the crash folder with support. This notification stays until you click Dismiss.
Anything else	`Prophouse: the editor crashed last session (the crash did not originate in Prophouse code).`

Every recovery notification has an Open crash folder link. If background previews are on, the message also says whether library processing has resumed and how many previews remain.

When the cause was a GPU fault and both Auto-generate 3D previews (background) and Bake preview textures (GPU) are on, the notification adds a Use geometry-only previews button. It turns off Bake preview textures (GPU) so previews stop using the GPU-heavy material bake. See Geometry-only previews.

If a Prophouse preview export crashed the editor, that asset is quarantined so the next run skips it. If the crash was a driver or memory fault, the asset in progress is not blamed and is processed normally next time.

The same message appears in the Prophouse panel header. To keep the Output Log line and the panel status but hide the notification, turn off Show crash recovery notifications under Advanced in Editor Preferences → Plugins → Prophouse.

Resumable imports

When an import starts, the editor claims the job on the server and saves the claim in the project. If the editor crashes mid-import, the next launch checks the job:

If the claim is still active, the editor resumes the import in the background and shows Prophouse: interrupted pull job #<id> finished after the restart. when it is done. A resumed import never opens the conflict dialog: every conflicting file keeps your local version, and the report records it.
If the server has already returned the job to the queue, the editor shows Prophouse: pull job #<id> was interrupted and has been returned to the queue — start it again from the Prophouse panel. Click Import on it under Pending imports.
If the job already finished, failed or was cancelled, there is nothing to resume.

If the editor is signed out, the server cannot be reached, or the desktop app cannot start, the saved claim is kept and the editor tries again on the next launch.