Troubleshooting

Start with the exact message shown in the Pluribus panel. Avoid clearing local state, creating duplicate workspaces, or sending a second confirmation request until you know which operation failed.

The plugin directory is read-only

Set a private writable data directory before starting ComfyUI:

export PLURIBUS_DATA_DIR="$HOME/.local/share/comfyui-pluribus"

Use the directory with one ComfyUI process at a time. Confirm the process can read and write it.

A Source Marker field will not update

Current ComfyUI builds open a small Value editor for the source key, display name, and note. Enter the value and choose OK before moving to the next field.

Choose a node-library result once. A double-click can insert two markers. If that happens, remove the duplicate and save the workflow.

Reference, LoRA, and unknown markers require a source key. A prompt-only marker may omit it only when a display name or note is present.

The sign-in message did not arrive

Check Spam before retrying or changing the email address. Confirm the address was entered correctly and wait for the current request to finish before making another one.

Fresh-signup inbox placement has a release-specific caveat. See the v0.4.0-rc.2 notes.

A returning owner is asked to create a workspace

Do not create a duplicate workspace. Reconnect the same owner account, refresh canonical state, and verify that the expected individual workspace is selected. If your team uses an invitation-controlled organization workspace, contact the Pluribus operator or support for the authorized selection path.

The project association disappears after restart

The first scan or project binding adds a private stable workflow key to ComfyUI metadata. Save the workflow after that first operation. Then restart with the same private data directory and reopen the saved file.

A write is slow or the result is ambiguous

Wait for a definitive success or error. A lost network response can happen after the canonical write or provider delivery attempt already occurred.

• Do not create a second project, person, or confirmation request blindly.
• Keep the request dialog open when retrying a confirmation request.
• Retry or reconcile the same stable request ID.
• If the dialog is lost, refresh canonical project state before taking another action.

The current release candidate has a specific link-only retry limitation after a dialog reload. See the release notes.

Disconnect appears to fail offline

An offline disconnect is not a successful revocation. The plugin retains the local token so you can retry. Restore service connectivity, choose Disconnect again, and wait for server confirmation.

Report an issue

Open a GitHub issue or email support@trypluribus.com. Include:

• Plugin release tag
• ComfyUI and Python versions
• Relevant node class names
• The exact panel message
• Whether the operation was local-only or paired

Do not attach private media, graph JSON, prompts, tokens, local paths, or client secrets. A minimal synthetic workflow is preferable when reproduction requires a graph.