The answer is not streaming
- 1Check your connection and keep the chat open for a moment; a complex first tool step can complete before visible answer text begins.
- 2Look at the status row and Activity for a running tool, required confirmation, cancellation, or structured failure.
- 3Use Stop once if you want to cancel. Do not submit the same message repeatedly while its state is unclear.
- 4Refresh the chat and check whether the completed answer was persisted before sending a clean follow-up.
A direct file upload is rejected
- Confirm the extension is listed by the current picker and the file opens normally on your device.
- Save legacy or macro-enabled Office files as a modern supported format, or export them to PDF or CSV.
- Reduce very large files, remove password protection, and split scan-heavy PDFs when practical.
- For reusable or larger material, upload it to a Workspace instead of attaching it to one turn.
A Workspace file stays Processing or shows Failed
Refresh the Workspace overview. Processing files are intentionally excluded from chat until indexing completes. Durable retries can resume after you leave the page, but malformed, encrypted, or scan-heavy documents may still end in Failed.
Use Retry once if offered. If it fails again, open the source locally, export a clean copy, and upload that copy under a clear filename. Keep the failed record and timestamp when contacting Support.
Computer or a tool was not used
Computer is not triggered by every file or the word “analyze.” Ask explicitly for the private Computer workspace when the task needs multi-file scratch work. Bounded attached-data analysis may be used when the capability is available; ordinary Fast answers favor a more direct path.
A short follow-up such as “try again” continues the latest explicit file task. For PDF edits, Chat should either create the edited download or state the concrete document limitation; it should not claim that PDF editing is unavailable.
A tool can also be unavailable because the selected model lacks the required capability, your plan does not include the feature, organization policy blocks the action, or the request can be answered more directly. LLMBase should state a material limitation instead of inventing a tool result.
An Artifact is missing or will not download
- 1Check that the assistant actually completed a create-artifact step rather than only rendering a table in the answer.
- 2Open the Artifacts library and find the file by its chat and creation time.
- 3On mobile, retry Download and choose a destination in the native share sheet.
- 4If generation failed, ask for the same bounded file again in a clean follow-up; do not claim the incomplete file is valid.
What to send Support
- The affected surface: web, iOS, Android, or desktop, plus the app/browser version.
- The chat or Workspace identifier, filename without sensitive content, and approximate timestamp with timezone.
- The Effort mode, selected public model ID, and exact visible error text.
- A sanitized description of the request and expected result. Never send a password, full API key, or unrelated private document.
Frequently asked questions
Should I keep retrying a failed tool call?
No. Retry once after checking the visible error and input. Repeated identical submissions can create confusion and make diagnosis harder.
Where do I contact Support?
Use the Support page or email support@llmbase.ai. Include a timestamp, affected surface, public model ID, and sanitized error details.