Halofy

When something gets stuck

Use Diagnose with AI to investigate an issue, or get help from Halofy support.

Start with Diagnose with AI#

When an error popup or error screen appears, click Diagnose with AI. Halofy opens a diagnostic chat with the error report and relevant app, provider and environment details already attached.

The agent investigates the available evidence and explains what failed and what to try next. Follow its suggested steps, or ask it to apply a fix. Diagnosis starts with investigation; changes require your instruction. You need a connected project and a working AI provider to start the chat.

Diagnose an issue directly from its error popup
A Halofy error popup with Diagnose with AI highlighted

02An agent won’t start#

Check its connection in Settings → AI services on the computer hosting the project. Confirm that the provider is enabled, installed and signed in. Follow the highlighted provider setup.

03A device is unavailable#

Confirm the host is awake and Halofy is running, then check the connection in Linked devices. Device connection guide.

04A file or preview is missing#

Ask the agent to deliver the file as an artifact. For a local website, confirm its server is running on the expected host and port.

05Still stuck?#

If the diagnosis does not resolve the issue, Halofy support is available. Share the error message, your app version, what you were doing and the steps you already tried. Include the diagnostic findings so support can continue from there.

A playbook or protected conversation is unavailable#

First read whether the message concerns a missing input, approval, connection, provider compatibility or required privacy. These have different fixes. Update Halofy on the computer doing the work, check the selected account and team, then follow the named requirement.

A reference-only playbook is still readable guidance. A guarded run requires compatible tools and a fresh conversation. A partial setup lists what was not collected and can run when the remaining checks pass. See playbook troubleshooting.

If a protected conversation loses its private state after a host restart, start a new compatible conversation. Halofy does not silently send an unprotected request when required protection cannot be established.

An unavailable Playbooks catalog gives you a retry action (example data).
An unavailable Playbooks catalog gives you a retry action (example data).
Privacy Protection shows the selected mode and whether a desktop update is required (example data).
Privacy Protection shows the selected mode and whether a desktop update is required (example data).

The message is paused before the agent starts#

For an expired sign-in, reconnect your Halofy account. For a temporary workspace check or rate limit, wait for the displayed delay. For a budget limit, ask your manager to review it. If a usage scan is still running, retry after it finishes.

Use Retry on the error when available, or resend once the issue is resolved. A paused message is not evidence that the provider received it. See workspace and budget pauses.

A budget notice explains why another turn is paused and who can raise the limit (example data).
A budget notice explains why another turn is paused and who can raise the limit (example data).