Troubleshooting

The usual suspects, in the order they usually turn out to be the answer.

If none of these fit, raise it with support

— include what you tried from this page.

The bot doesn't reply at all

  1. Is the instance running? Check the dashboard — a stopped or still

provisioning instance answers nobody. Start it, or wait for

provisioning to finish.

  1. Are you approved to talk to it? The assistant ignores senders it

doesn't know:

  • Telegram — you must have pressed Start in the bot chat after

deploying; the approved users are listed in the Channels tab.

<!-- Withdrawn 2026-08-19 (restore with ChannelsTab.jsx):

  • Discord / WhatsApp — first-time senders get a pairing code

that has to be approved in the Channels tab. Check for a pending

request.

-->

  1. Still nothing? Use Restart Gateway on the Server tab (it's

safe and doesn't touch billing), wait a minute, and try again.

The bot replies with an error about its AI provider

Nine times out of ten the key is fine and the provider account is the

problem:

  • Niva AI credits (you never entered a key) — the advice below is for

bring-your-own accounts; check your credit balance first — see

My assistant stopped replying and my AI credit shows R 0.

  • OpenAI — API billing is separate from ChatGPT. Add a payment method

or credits in the platform's billing settings.

  • OpenRouter / DeepSeek / Moonshot — prepaid balances. Top up.
  • Any provider — if the configured model was deprecated or your

account lost access to it, switch models

(how).

  • Subscriptions (ChatGPT, Claude) — heavy use can hit your plan's

usage cap; it resets on the provider's schedule, not ours.

My assistant stopped replying and my AI credit shows R 0

Your credit ran out. This is a stop, not a fault — the assistant has

nothing to think with until you top up:

  1. Nothing else is lost. Your instance is still running, and your

settings and history are untouched.

  1. It wasn't silent. Warnings went out twice on the way down — once

when credit got low and again when it was nearly gone. On Telegram they

arrive in your chat with the assistant; on any channel they're emailed

to you, and a banner appears on the Providers tab.

  1. The fix is a top-up. Open the instance's Providers tab, choose

an amount and pay (details). Replies

resume on their own — no restart needed.

My AI credit top-up was declined

The decline message comes from your bank, not from us, and **nothing

was charged**. Don't keep pressing the button — every attempt is a real

charge against your card, and banks lock cards after repeated declines.

Check with your bank or use a different card, then try once.

If the panel says a top-up is already going through, that's the

opposite situation: give it a moment rather than paying twice.

I can't change how clever my assistant is

Two usual causes, in order:

  1. "Waiting for a software update" — your instance's software predates

this setting. That's a rollout on our side, not something you did — try

again later.

  1. The instance isn't running — the setting is applied on your server,

so start the instance first.

The AI credit balance looks out of date

It can be, slightly — the balance is checked in the background, not read

live, and runs up to about five minutes behind. That's why the panel

says "as of \<time\>" under the figure rather than pretending to be

live. Recent use catches up on its own; a successful top-up is confirmed

on the spot.

I want annual billing with AI credits

Not available — an assistant on Niva AI credits bills monthly,

and the annual option is hidden at checkout when credits are selected. If

annual billing matters more to you, deploy with your own provider account

instead (options).

The Claude approval code "expired" or the connect wizard failed

The approval code is only valid for about two minutes. This is normal

— nothing is broken. Use the wizard's start-over button and paste the code

promptly this time.

Connecting a ChatGPT or Claude subscription is greyed out

Subscription connections need a running instance — they're set up from

the dashboard after deploy, not during the wizard. Deploy first (with any

key, or keyless for Claude), then connect.

<!-- Withdrawn 2026-08-19 (restore with ChannelsTab.jsx and docsCatalog.js):

WhatsApp stopped working

WhatsApp unlinks devices sometimes — notably if your phone is offline for

around 14 days, or if you logged the device out from your phone. Open the

Channels tab: if the panel shows disconnected, run the QR login again

(steps).

-->

A channel or provider action fails with a server error

  • If the message says your instance needs a software update, that's on

us, not you — raise a support ticket and we'll update it.

  • If the dashboard can't reach your server at all, raise a support

ticket.

"Payment failed" banner on your instance

Your subscription payment didn't go through and the instance is in its

grace period. Update your payment method under Billing before the

countdown ends (details).

<!-- Withdrawn 2026-08-19 (restore with ChannelsTab.jsx and docsCatalog.js):

Discord bot is online but ignores messages in the server

Almost always the Message Content Intent toggle — it must be enabled

on the Bot page of the Discord Developer Portal

(steps). After enabling, give it a minute, then

try again.

-->