Rendering and Recovery

Follow queued work, stop deliberately and recover without duplicate submissions

Last updated: 2026-10-27

Start and Follow Work

Choose the intended source, recipe and output before starting a render. Check model availability and licence requirements first. Keep the app running while local work is active; a queued job is not a cloud service that continues after all local processes exit.

RENDER submits work for execution. The header queue's + action parks a prepared render for later without starting it. Open the queue and choose that parked item's Run when ready. For an existing render, check the Render action menu's Current pass/All passes choice before submitting; see Multipass for append scope.

Open the header's render queue to inspect work. Up next is waiting work; active rows show progress. Parked work needs its Run action rather than being assumed to start automatically. Open a row to inspect its owning render. Library's Queued filter also helps find active queued/parked work. Paused, waiting and running are different states; read the item's message rather than using a percentage alone to judge whether it is stuck.

GPU busy means another operation may own the device. Wait for that operation's settled result, reduce workload where appropriate or use its supported Stop control. Do not clear lock files, kill unknown workers or start another copy of the app merely to bypass busy. A model fit estimate does not reserve memory.

Cancel and Stop

Use Cancel for waiting work or Stop on the active operation's own control. The label and effect depend on the subsystem. Stopping/Cancelling means a request is pending, not that the worker has exited. Wait for confirmation before starting conflicting work or switching Projects. An unconfirmed stop remains uncertain; inspect the item again instead of assuming the request succeeded.

Closing a tool, dismissing a progress panel or disconnecting an agent does not necessarily cancel accepted work. Completed frames/variations can remain after cancellation, and saved edits are not universally rolled back. Discard of a held preview and stopping a render are separate actions.

After a Lost Reply or Crash

  1. Note the task, render/sequence name, approximate time and destination. Preserve any receipt/job identifier and error text.
  2. If the app is still running, inspect the existing queue/item and destination before submitting again. A timeout can happen after work was accepted or saved.
  3. If it exited, reopen normally and read startup warnings. Check the active Project, configured drive and Settings > Storage fallback status before concluding that work disappeared.
  4. Inspect saved output/history and the owning tool's recovered state. Decide explicitly whether to resume, retry only missing work or keep an existing result.
  5. If recovery is refused or the outcome remains unknown, preserve files and use Send Feedback. Do not delete recovery state or repeatedly restart to make a blocker disappear.

Startup can reconcile interrupted work and recover some queues. It does not promise automatic resumption of every job or preservation of all unsaved state. A startup-complete message does not prove a remote upload or export completed.

Recovery Depends on the Task

Task Inspect before trying again
Render/history edits Existing item, saved versions and any held drafts; a visible preview is not proof of a committed output.
Image/Dome/Unreal export Chosen destination and result paths/receipt; an unknown response can conceal a written or partially delivered file. See image export.
Ordinary sequence Completed frames, frame failures and current status; follow Sequence and sequence export rather than rerunning completed frames blindly.
Native Shader sequence Existing destination and recovered status; folder inspection offers explicit Continue for a matching unfinished job and Open folder for completion. Continue verifies files; conflicts preserve them. Restart does not automatically restart GPU rendering. See Shader.
Fractal scene/sequence Save/Check save/Finish adopting when offered; scene adoption, retained masters, folder output and encoding are separate outcomes. See Fractals.
Folder Format Converter Existing completed files and errors. Its jobs are not a durable restart queue; preserve outputs and prepare remaining inputs plus a fresh destination. Same-name files can be overwritten on rerun. See Format Converter.
Model download Model Manager's queue, partial download and repair/retry state. Do not delete weight folders to resolve a transient wait. See models.
Gallery upload The connected account, remote item and processing status. Check for an accepted entry before uploading again. See Gallery Publishing.
Copilot/MCP action Its receipt/status and saved target before approval or resubmission. Chat text alone does not establish a completed mutation. See Copilot.

Before a Planned Restart

Let work settle, save editable scenes and commit or deliberately discard held previews. Export important completed results and make a backup before relocation or destructive cleanup. Restart normally when a setting requires it. Forced process loss can lose in-memory state; it is not an ordinary recovery step for every failure.

Esc
Searching...
No results found.
Type to search the documentation
↑↓ Navigate ↵ Select Esc Close

We use cookies for analytics to understand how visitors use our site. Privacy Policy