Troubleshooting
Start with what you see. Change one thing, then check the result.
Before trying again
- Read and keep the exact error text. Note the task, selected model, and source.
- Keep useful input and output, especially if saving failed.
- Do not clear app data, delete a project, or repeatedly submit the same task as a first step.
Cannot send or generate
On a narrow screen, scroll the table sideways to see all columns.
| What you see | Check first | Next step |
|---|---|---|
| Button disabled | Required input, chosen model, and whether a task is already running. | Complete the missing field or handle the running task before trying again. |
| Model unavailable | Connection state and account access. | Fix the model connection, then select an available model for this task. |
| Waiting for approval | The pending operation in this conversation. | Read its target and scope, then allow or refuse it. |
| Stopping / reconnecting | Whether the current run has actually ended. | Wait for a clear state; preserve input and report persistent problems. |
| No usable output | The exact error and whether the chosen workflow and model are available. | Keep the material; correct the reported issue before another call. |
Model connection errors
| Symptom | Check |
|---|---|
| Authorization failed | Credential validity, subscription authorization, and permission for the chosen model. |
| Model not found | Exact model ID and which connection supplied it. |
| Quota or rate limit | Usage on the selected platform, API, or subscription account. Avoid repeated immediate retries. |
| Connection or timeout error | Provider address, network connectivity, and provider availability. |
| Listed but call fails | Listing and a successful live call are different checks; read the actual call error. |
A file or source was not used
Check whether the correct file was selected, whether reading completed, and whether it was included in this request. Knowledge must be selected deliberately. If the app cannot read the format, paste the relevant text and retain the source name.
A link, file name, or source badge alone does not prove that its entire content was available. For a long source, identify the passage needed for this task.
Review material choices →Cannot find a saved draft
Confirm where it was saved
Was it a conversation, workshop draft, library document, or project file? Return to the corresponding space.
Clear search and filters
In the library or conversation search, clear narrowing filters and check archived records where available.
Confirm the device and workspace
Desktop material does not automatically appear in the web account. Return to the device and workspace used for saving.
Handle save failures carefully
If the current page still holds the content, copy it before restarting. Report the exact save error rather than clearing data.
A project cannot be opened or run
Confirm the selected folder and whether it was moved, renamed, or disconnected. If the app says it cannot open the project, use Add project folder to select the intended folder again. Keep the existing files.
If generated output runs incorrectly, describe the action you took, the input, the expected result, and the observed result. Paste relevant error text. Ask for a focused repair and retest the same input after the change.
I opened the page and selected the practice CSV. I expected Books 30, but the page shows Books 20. Check the grouping and summation logic; keep the file local.
The draft is inaccurate or does not fit
Point to the unsupported sentence and compare it with the source. Correct the material or writing requirements, then revise only the affected part when possible. For a different tone, say what should change and what must remain.
A fluent draft, a source label, or a successful request is not a factual review. Names, figures, conditions, and personal experiences still need your check.
Send a useful problem report
Include the app version, macOS version, whether you used desktop or web, the task steps, selected model and source name, exact error, and what you expected. Screenshots can help after private content is removed.
Do not send API credentials, login codes, full private project folders, or unrelated personal documents. A short reproducible example is more useful than an entire archive.
Open contact and feedback →