Troubleshooting

ComfyUI startup and process ownership

The app checks capabilities automatically when Grimoire’s custom ComfyUI runtime becomes ready and retries failed connection checks with a delay of up to 30 seconds. You normally do not need Retry while the server is loading. Checking means a connection check or startup is still in progress; Available means the server returned its capabilities. If a saved server process cannot be verified, the app can still connect to its endpoint for AI requests. Stop, restart, and changes to runtime files remain blocked until ownership is verified; this prevents controlling an unrelated process. Ownership is checked again automatically, and stale records for exited or recycled process IDs are cleared. If the warning persists, open AI → ComfyUI Runtime → Diagnostics to inspect the saved process and runtime path. Automatic startup problems appear in status rather than repeated alert popups.

Start with the error text and the selected workflow. Connection, capability, source, processing, and import failures have different fixes.

Start with what you can see

Server unavailable

Open AI → ComfyUI Runtime and check the status and logs for Grimoire’s custom installation. If installation is incomplete, finish and verify it through the Install Wizard. Start the runtime, wait for Available, then refresh models. A busy runtime and a disconnected runtime are different states.

Missing model or node

Install the required model pack through Model Management and verify the custom runtime through the Install Wizard, then refresh metadata. Match diffusion model, encoders, VAE, LoRA, and guidance family. An empty selector is not fixed by typing a prompt.

Resource failures

Reduce dimensions, batch/output count, or animation length. Check available GPU/system memory and the selected acceleration backend. After a backend failure, use runtime controls and inspect logs before resubmitting; repeated larger requests are unlikely to help.

Source or mask problems

Confirm active frame/layer, source-picker mode, reference assignments, and editable layer type. For In / Outpaint, check canvas transparency, the current selection, and the selection/invert/grow controls. Heal/Clone require sampling a source again after cel changes. Mixel Heal can legitimately leave ambiguous fringes untouched.

Blank or cropped result

Check the preview before import, selected outputs, destination, layer visibility, current timeline frame, covering layers, and size policy. Crop to canvas can omit output outside the canvas; choose Scale to fit or Grow canvas when appropriate.

Reporting a problem

Record the app version, platform, tool, backend, model family, steps to reproduce, and error/log excerpt. Remove API keys and personal paths/artwork before sharing. Include a small sample when the issue depends on a brush fringe or mask.