Troubleshooting

This guide covers common issues you may encounter while using Neotask and how to resolve them.

Check Gateway Health Before Applying Repairs

Neotask has separate screens for connection status, runtime health, the combined system report, and automated repairs. Use them in this order.

1. Check The Connection Path

  1. Open Settings → Infrastructure → Connection.
  2. Confirm the path from Desktop app to Local gateway, Neotask cloud, and Connected services.
  3. Read the first stage that is not ready.
  4. Use Start or Restart under Gateway controls when the local Gateway is stopped or stale.
  5. Refresh the page and confirm that every stage is ready.

Gateway connection path and Gateway controls

2. Run The Runtime Health Check

  1. Open Settings → Infrastructure → Health.
  2. Click Run check.
  3. Review event-loop delay, active work, queued work, channels observed, and recent stability events.
  4. A high queue, delayed runtime, or dropped diagnostic events can explain slow or stalled work even when the Gateway is connected.

Runtime Health with responsiveness, workload, channels, and stability checks

3. Review The Combined System Report

  1. Open Settings → Advanced → System report.
  2. Review Local gateway, Session access, Runtime response, Connected services, Current work, and Scheduled checks.
  3. Start with the first item that needs attention.
  4. Copy the sanitized report when support needs the full result.

System report with live Gateway and service checks

4. Run The Doctor And Apply Repairs

  1. Open Settings → Advanced → Troubleshoot.
  2. Click Check system. This check does not change your installation.
  3. Select Show technical output to read the detailed findings.
  4. Click Apply repairs when the check makes it available.
  5. Keep Settings open while Neotask applies repairs and runs the follow-up check.

Troubleshoot settings with Check system and Apply repairs

Retry the original action after the follow-up check completes. If it still fails, copy the technical output and include it when you contact support.

Additional Checks

External Dependencies with installed optional components

The Logs screen is local and redacted. Use it when the health screens identify a runtime or service problem that needs event detail.

Redacted local Gateway Logs


License & Activation

"Invalid license key"

"License revoked"

"License expired"

"Offline grace period expired"

"Version blocked"


Gateway Issues

"Gateway failed to start"

  1. Fully quit Neotask and open it again.
  2. Open Settings → Infrastructure → Connection and check the Local gateway stage.
  3. Use Start or Restart under Gateway controls.
  4. Open Settings → Advanced → System report and review the live system checks.
  5. If the Gateway still fails, run Check system from Settings → Advanced → Troubleshoot.
  6. Review the first failed item in the technical output.
  7. Click Apply repairs when it is available.
  8. If the follow-up check still fails, copy the technical output and send it to support.

"3-strike lockout"

"Gateway disconnected"


Voice Issues

"No audio input detected"

"Wake word not triggering"

  1. Ensure voice activation is enabled in Settings
  2. Check that wake mode is set to "Porcupine" (not "Shortcut" or "Off")
  3. Say the wake phrase clearly: "Hey Neotask"
  4. Try the keyboard shortcut instead (Cmd+Shift+Space / Ctrl+Shift+Space)
  5. Check if another app is using the microphone

"TTS audio choppy or delayed"

"Voice shortcut not working"


Connection & Network

"Cannot connect to server"

"API request failed"


Agents & Sessions

"An external app is missing from Import"

The import list is detected-only. An app appears only when Neotask finds eligible local material, not merely when the app is installed. Confirm its local home contains supported active setup or recent sessions, then open Settings → Import and select Check again. Credential-only, archived, deleted, hidden, cache, log, and telemetry state is intentionally excluded.

For provider-specific paths, Code-vs-Chat routing, idempotency, audit-trail behavior, MCP credential portability, and verification, see Import From Other AI Apps.

"Cannot create agent: limit reached"

"Agent not responding"

"Session messages not loading"

"Interrupted by restart" or "Resumed after restart" in the activity feed

These two entries are normal. Interrupted by restart marks work that stopped because of an app update, an operating-system restart, a crash, or a power loss. Resumed after restart marks the same work starting again.

If you see Interrupted by restart with no matching Resumed after restart:

  1. Open Settings, select Automations, and confirm Continue work after restarts is on.
  2. Open the company, select Settings, and confirm that company is not overriding the setting to off.
  3. Remember that work waiting for your approval is recorded but never resumed automatically, and neither are runs that failed for a reason other than the restart.

See Continue Work After Restarts.

"Send a message to continue"

A thread that cannot be continued automatically, for example when the assistant session has expired, shows Send a message to continue instead of resuming on its own. Send a message in that thread to continue working. Your original message is never sent twice.


Billing & Payments

"Payment failed"

"Usage allocation exceeded"

"Plan not updated after payment"


Performance

"App slow on startup"

"High CPU usage"

"High memory usage"


Getting Help