Troubleshooting common errors
Find the message you see, check the right account or runtime, and take the next useful step.
Unauthorized or verification problems
A 401 Unauthorized response means the endpoint did not accept your signed-in session. Sign in again and retry from the app. If it persists, report which action failed and when. Some older callers do not send the authentication header that their endpoint requires; repeating the action will not repair that caller.
For a missing verification email, check spam and use Resend verification. After opening the email link, choose Already verified? Refresh status. An email signup and a paid LaunchPad subscription are separate steps.
No active Launchpad subscription or product not included
No active Launchpad subscription (402) means the LaunchPad account record has no plan. Check that you used the same account at checkout and on the agent dashboard. A main-account plan does not automatically create a LaunchPad plan. If payment completed and the plan is missing, send support the receipt and account email.
Your plan does not include this product (403) means a Solo plan is being used to launch the other agent. Open the included product or review Bundle on LaunchPad. Price not configured and other checkout setup errors require an operator fix; changing your card will not fix missing price configuration.
Hour cap, inference cap, or insufficient balance
Hour cap reached and inference cap reached refer to LaunchPad. Check both gauges on the agent dashboard. Your provider's own account is billed separately. A hard-stopped account may remain blocked after connecting a provider, so contact support if the flag persists.
Insufficient credits refers to older chat credits. Insufficient balance refers to the proxy wallet. Neither is the LaunchPad inference gauge. If a paid top-up has not appeared, report the receipt instead of retrying the payment. A rate-limited model error in older web chat suggests retrying in 20 to 30 seconds.
Channel fails to connect or no QR appears
No sandbox provisioned (404) means the older OpenClaw sandbox is missing. Sandbox not ready or Sandbox is stopped (503) means that runtime must be started before connecting. Open the older runtime page, rather than assuming a running LaunchPad card is the same sandbox.
Channels require Starter plan or above (402) is the endpoint's older wording for its main-account plan gate. Missing required field (400) means a required connector field is blank. A separate setup flow (422) means the generic token endpoint cannot pair that channel; WhatsApp uses its QR flow.
For WhatsApp pairing failed or Gateway stopped unexpectedly, check the runtime state and start pairing again. A connected badge alone is not proof of message delivery. Send a test message after setup.
Saved settings did not change the agent
The older personality editor saves a stored file record, not a live sandbox file. Its API key editor explicitly requires reprovisioning. Check which dashboard owns the running agent before editing. If a save or restart gives Unauthorized, report that exact action to support.
Send a useful support report
Include the page URL, action, exact error text with private values removed, time and timezone, and whether you are using LaunchPad or the older OpenClaw runtime. For billing, include a receipt reference. Never send passwords, API keys, bot tokens, provider login codes, or QR session data.