NeurionReference
Troubleshooting
Resolve sign-in, tool, task, schedule, and update problems without repeating uncertain actions.
HydraLabs · Published
Sign-in or payment does not finish
- Return to Neurion and check the account shown in the desktop.
- Confirm that the browser used the account and workspace you intended.
- Cancel an expired desktop connection attempt and start a fresh one from the application.
- After checkout, inspect the existing payment in Billing and refresh account state before starting another checkout.
- If the account check fails, retry it rather than assuming the subscription is absent.
A successful browser sign-in and a connected desktop session are separate results. Keep the original desktop request open while completing the browser flow.
A tool, connector, or skill is missing
Check the capability’s enabled state, required configuration, authentication, connection status, and task scope. Installed does not mean connected, and enabled does not grant every action supported by the tool.
For MCP, inspect the server’s current tools and its configured product. A Code-only connector does not appear as a Chat tool. Reconnect or finish authentication before starting work that depends on it.
For skills, check that the guidance is installed and enabled. A connected MCP server does not automatically install a matching skill. Computer Use’s desktop entry points are not exposed in the current interface.
For CyberBot, open the environment manager. Review compatibility and storage, then use Prepare or Repair as requested. If Windows reports a pending restart, complete it before trying again.
A task stopped or has an uncertain result
Reopen the conversation and inspect the latest status, tool result, files, and pending approvals. Determine whether the work completed, failed, was canceled, or has an outcome that still needs verification.
Do not repeat a payment, external message, deletion, publication, or other consequential action solely because its final confirmation is missing. Check the existing operation first.
A network error after a request was accepted does not prove that nothing happened. Preserve the task and operation references when reporting the issue.
Changes or an update cannot be applied
For code conflicts, inspect the current destination files and the task’s worktree. Preserve both sets of changes until you understand the conflict; do not overwrite later edits to force an earlier diff to apply.
For a desktop update, check available disk space and connectivity, save work, and use the update’s retry action. If setup is still running, let it finish before launching another installer.
If package verification or startup fails, record the exact error code and application version. Use the official installer or contact support; do not disable package verification or replace application files from an untrusted source.
Create and troubleshoot scheduled work
Open Scheduled to create a local schedule. Enter the task instructions, choose the available project or conversation target, set the recurrence and timezone, then review the next-run time before saving. Use the same controls to pause, edit, or remove a schedule.
Scheduled work runs locally. Neurion must remain open, the device must be awake, and the connected account and required tools must be available. The scheduler does not wake the computer or run in the cloud while the application is closed.
- Open Scheduled and check that the schedule is active.
- Confirm its timezone, recurrence, project, and selected task.
- Inspect the run history and the recorded error or skipped occurrence.
- Check account access, usage, tool availability, and any pending approval.
- After an uncertain run, review its result before resuming or running it again.
Create and edit schedules through the available Scheduled controls. Use a supported recurrence and review the displayed next-run time. Missed occurrences are not evidence that the work was completed, and an uncertain run can pause its schedule for review.
Send a useful support report
Contact support@hydralabs.ai with the application version, affected feature, expected result, actual result, exact error, and the steps that reproduce it. Include the relevant task or transaction reference when one is available.
Attach only the diagnostics needed to understand the problem. Remove passwords, API keys, session cookies, payment details, and unrelated personal content from screenshots and logs.
Keep the original local files and task history until the issue is understood. A screenshot is useful evidence of a visible error; it is not a substitute for the version and reproduction steps.