Guides

Troubleshooting

Common issues

”Device not found” when starting a run

  • Make sure the Chrome extension is installed and the side panel has been opened at least once (this triggers device registration)
  • Run reduck devices to verify your device is listed and selected
  • Try disconnecting and re-pairing the device

Run starts but no progress events

  • Check that Chrome allows notifications for the extension (OS settings → Notifications → Chrome)
  • The extension service worker may have been stopped by Chrome — open any extension page to wake it up

Budget exhausted

  • Your monthly budget is exhausted. Check usage on the dashboard
  • Upgrade your plan or wait for the next billing cycle

Extension crashes during automation

  • Check chrome://extensions → Reduck → Errors for crash logs
  • Common cause: the target site loaded a resource that conflicts with the content script
  • The run will eventually time out and emit a failure event

Authentication error when starting a run

  • Your API key is invalid or revoked — check REDUCK_API_KEY or run reduck login again
  • Generate a new key from the dashboard if needed

CLI hangs after Ctrl+C

  • The CLI sends a cancel request then exits. If the runner is unreachable, it may take a few seconds to time out
  • Force quit with Ctrl+C again

Push notifications not working on macOS

  • Go to System Settings → Notifications → Google Chrome → allow notifications
  • Chrome must not be in “Do Not Disturb” mode

Debug tips

Check if your device is reachable: Open the extension side panel — if it shows “Connected”, push notifications should work.

Test with a simple query first:

reduck -q "Go to google.com and tell me the page title"

If this works, the issue is with the target site, not Reduck.