Troubleshooting
Recover from common connection, confirmation, file, notification, search, and access problems.
Begin with the smallest boundary
Write down the affected user, workspace, conversation or record, exact time, and exact message. Check whether the problem affects one request, one user, one browser, or everyone. Do not reset the workspace or delete history as a first test.
Chat has no usable AI connection
Open Settings > General and read the connection status. An administrator can then open AI models to reconnect, replace an expired key, or check the saved order. Test with a new read-only conversation after the connection becomes usable.
A confirmation cannot be prepared
If a card says the confirmation could not be staged, the requested change should not have happened. Check the underlying record once. Refresh the conversation and prepare the action again once.
If the same storage error affects every write for one user while other users work, stop retrying. Create a Support ticket with the user, site, time, action, conversation, and full error. Do not delete the user’s history; it may contain the evidence needed to diagnose the failing storage boundary.
A file remains in Processing or Error
Open the File Box item and check its status. Make sure the file is complete, readable, and not password protected. Try one clean source file rather than uploading the same large batch again. Keep the original until the prepared work is checked.
A browser notification does not appear
Check Settings > General > Notify when a reply is ready, then check the browser’s permission for this exact workspace address. A missed browser notification does not remove the chat reply or Approval Board item.
Search or a list does not show expected work
Clear every active filter, check the sort and page, refresh, then search by an exact record number. If another user can see the record and you cannot, ask an administrator to check your Frappe access.
A scheduled routine did not run
Check that the Macro, Trigger, or Agent is enabled. Read its schedule, time, daily cap, last run, and Activity or Runs history. A skipped run is different from a failed or blocked run; open the detail before changing the schedule.
Send a useful support request
Include what you expected, what happened, where it happened, the exact time, the smallest known affected group, and a screenshot with secrets removed. Never include passwords, private keys, payment details, or full access tokens.
For a complete example, follow Report a problem with everything support needs.