Troubleshooting
Find a symptom and check accounts, models, connections, apps, and local services.
Record your version from Settings → About. Change one setting at a time and repeat the original action so you can identify what helped.
Sign-in fails or the device limit is reached
Check connectivity, the account, and the service address. If the device limit is reached, revoke an unused device from the account's device list. Refresh account status after a plan change. Cloud features require connectivity even if an offline license is valid.
See account and usage.
A model fails or is unavailable
| Symptom | Check |
|---|---|
| Official model is unavailable | Sign-in, access, allowance, service status |
| Custom provider rejects authentication | Key, URL, provider account, quota |
| Model list is empty | Save, refresh, and enable the model |
| Local model cannot connect | Local service, address, installed model |
| Text works but images fail | Image input support |
| External agent fails to start | Installation, sign-in, and runtime under Agents |
Chat allowance and media Credits are separate. See model setup.
Search or a connected app fails
- Search: inspect Settings → Web search, separately from model settings.
- Authorization succeeded but the app did not open: allow the browser to open Nexts or return manually and refresh connections.
- One account expired: reauthorize that account in the service details.
- Authorization is not configured: inspect the service message or contact support.
- Chrome will not connect: check both the Nexts plugin and browser extension; follow the Chrome guide.
Files or generated results are missing
Check the selected project, attachment status, file locks, and permissions. Ask for the actual saved path and open it from the workspace or Bot folder.
Restore archived chats from settings. Deletions are not always reversible; clearing data is not a first troubleshooting step.
A Bot does not remember something
Confirm the Bot identity, independent-memory setting, and whether the information was saved. Edit outdated notes in its details. Independent memory is not automatically shared between Bots.
An app will not install or start
Check platform compatibility, version, installation rights, and download status. Finish any separate Windows installer. If the program is not detected afterward, choose Detect again.
Inspect background-service logs before restarting. Uninstalling and deleting data are different; see Install and Manage Apps.
Skill recording produces no result
Use Windows desktop with the recording component enabled. Stop and save the recording, then check the model and conversation. The workbench's Open in chat to create Skill prepares a draft that you still need to send. See skill recording.
A scheduled task did not run
Check enabled state, timing, repeat rules, and whether Nexts was running on an awake computer. Inspect the run record to distinguish a missed trigger, failure, and an approval wait. Cloud services also require network access and valid authorization.
A phone cannot connect
Check host connectivity, remote service, account, and device status. Refresh used or invalid pairing codes. Full desktop access requires Remote desktop control separately. See remote access.
Canvas generation fails
Check links, reference assets, supported model parameters, channel, and allowance. If the outcome is unclear, inspect job status before resubmitting to avoid duplicate generations. See Canvas.
Updates or core services fail
Check Settings → About and finish any requested restart. For repeated startup failures, inspect Logs & diagnostics and export a local bundle.
Contact support
Send info@nexts.ai your version, operating system, failure time, minimal reproduction steps, expected and actual results, and exact error message.
Include only necessary, reviewed screenshots or diagnostic excerpts. Exporting a ZIP does not send it. Earlier sensitive debugging may have captured private content; inspect logs and remove credentials, pairing codes, and unrelated material before sharing.