Diagnose a Failed Response Safely

Start with evidence and narrow the failure before changing services, models, or stored data.

Steps

1. Record the exact user-facing error message and the time it occurred.
2. Check application and model-service status without restarting anything.
3. Retry with a shorter prompt and no attachments.
4. Add attachments back one at a time to isolate file-specific failures.
5. Record the conversation identifier, selected model, and reproducible steps.
6. Use the approved diagnostic or support route if the problem remains.

What success looks like

You can identify whether the failure follows the prompt, attachment, selected model, or service state without losing useful evidence.

Protect sensitive information

Do not include passwords, API keys, session data, private document contents, or other secrets in support notes.

Attach and verify a document · Support · Back to Help Center

Last reviewed: July 21, 2026. Applies to the FridayLocalAI Alpha release.