Quick start
Troubleshooting
Locate sign-in, capture, AI, asset and platform delivery problems before retrying.
Updated
Record the entry, workspace and time, then read the current state. Repeated workspaces, uploads or generation requests make diagnosis harder.
Check the workspace and whether you are viewing local or cloud data. Check filters and categories. Mobile does not display a computer's full local workspace. For cloud content, check connectivity and account status.
Switch Collect inspiration to Inspiration backlog and remove unnecessary filters. If content is still missing, check the original workspace or import record.
Distinguish upload, body extraction and attachment errors. Try the extension for a page requiring sign-in, or supply an excerpt with its source. Retry only failed files in a batch. See Capture.
Look for pending questions or approvals. Then check the execution option, node status, model availability and usage allowance. Desktop sleep can interrupt local tasks. Keep the original conversation and error before correcting the conditions and retrying.
Check whether the reply includes a saved output. Ordinary chat text does not necessarily create a separate document; copy it to a knowledge-base note if needed. For an existing file, check the matching conversation or project category.
Refresh the item and try preview or original download again. Keep the filename and error if it fails; do not delete the original first. Open unsupported preview types in a suitable local app after download.
The date records a plan. Check review, execution and target account. A saved draft is in the platform draft box, not necessarily on its public page.
Look for an existing draft before retrying. Restore an expired platform session first. Repeating an unknown result can create duplicates.
Prepare device and app version, workspace identifier, conversation or task ID, time, error and steps already tried. Remove cookies, tokens, API keys and private text before using Contact.
Q: Should I delete a failed task before retrying?
**A: ** Keep the original conversation, task identifier, and error so you can locate the failure. For platform delivery, check for an existing draft before retrying.
Q: Can I attach a complete log when reporting a problem?
**A: ** Inspect it first and remove cookies, tokens, API keys, and private content. Keep the device version, workspace and task identifiers, time, error, and steps already attempted.