When a seat does not answer, or the room says it skipped one, the seat's own Test button is the quickest way to the cause. Open Settings → Who's In The Room, find the seat and press Test. It makes one small call the way a discussion would — on the seat's current model, through the seat's own Runs On choice — and reports what came back. A test is not charged to your credit.
What Test tells you
- No credit left. Top up to use Our Keys. The seat runs on Our Keys and the balance is empty. Top up in Plan & Billing, turn on auto-reload, or switch the seat to your own key.
- No key for this model yet. The seat is set to your own key and none is saved for that vendor. Add the key, or set the seat back to Our Keys.
- This endpoint has no key yet. A custom endpoint whose address changed needs its key typed again for the new address.
- An error from the provider. A wrong or revoked key, a model the key cannot use, or the provider being down. The message is the provider's own; check the key in the provider's console.
A seat the room skips
A seat that is off, has no key, or is not installed is skipped rather than waited on, and the room says so under the turn. On the free plan, a seat on your own key, a custom endpoint, your company's cloud or a CLI works for one 14-day trial, then needs Pro; Our Keys and Free Key keep working.
On the Mac
A CLI seat is checked differently: Test re-runs detection and reports where it looked. If it is not found, or its sign-in has lapsed, see "A CLI seat isn't found, or ltb hangs" and the OAuth troubleshooting article.
Still stuck
Send us a message from this help centre with what Test said; the exact words save a round of questions.