GuidesTroubleshooting
What Keenoble's error states mean, and what to do
Every failure in Keenoble is meant to name itself. A reference for the messages you can hit in Chat, Compare, Preview and Code — and the fix for each.
Draft — not yet walked in the live product
All 10 steps below were written by reading the Keenoble source rather than by performing them, and each unwalked one is tagged [UNVERIFIED]. Reading a component tells you what a control is labelled; it does not prove the control is reachable, that the order is right, or that the result is what the text says. Until a reviewer has walked every step, this page is excluded from the sitemap, marked noindex, and publishes no structured data.
Before you start
- An error on screen.
Steps
“<Model> is unavailable right now.” — your named model could not answer. Click “↺ Retry with Auto” to send the same message through Smart Routing instead. [Unverified]
Keenoble will not quietly answer with a different model than the one you picked. The button is the explicit way to accept a substitute.
“That took too long to answer — please try again.” — the request timed out. Send it again; if it is a long task, consider splitting it. [Unverified]
A short apologetic line ending “— please try again.” — a genuine failure somewhere in the request. Retry. If it repeats, note the request id from the receipt on a nearby answer and send it to support. [Unverified]
The same line is used as a backstop when a request technically succeeded but produced nothing to show. A blank answer with no error is never an acceptable final state, so you get this instead.
“⏹ Stopped” — you stopped the answer mid-stream. Whatever had already arrived is kept; “(stopped before any response)” means nothing had. [Unverified]
“Build routing failed. This looks like a server error page, not a valid AI response.” — a server error came back where an answer should have been. Retry, or simplify the request. [Unverified]
A red column in Compare — read its headline and its detail line, then use “Retry this column” if it offers one. The other columns are unaffected and are not re-charged. [Unverified]
“Build output rejected” or “Build stream failed” in Preview — use Retry, Simplify prompt, or Restore previous, as described in the Preview recovery guide. [Unverified]
“Preview couldn't render — your previous site is still saved.” — the render failed, not the build. Send another message to try again; nothing you had was lost. [Unverified]
“Connect GitHub first” or “No changes to push” in Code — exactly what they say. Connect in the Git panel, or make an edit before pushing. [Unverified]
“Couldn't save — try again.” after picking a compare winner — the vote did not reach us. Click again. [Unverified]
The rule these all follow
An error in Keenoble names what happened and what to do about it. It does not present a failure as a success, does not substitute a different model without saying so, and does not show a thank-you for something that did not happen.
If you find a message that breaks that rule, it is a bug and we want it: support@keenlabs.pro. Include the request id from the receipt.
If nothing on this page matches
Open the receipt on the nearest answer and copy the “Request …” id. That id identifies the exact request in our logs, which is faster than any description of the symptom.
Next
Having problems with the platform? Contact us at support@keenlabs.pro. If a step here does not match what Keenoble does, the step is the bug — send it to the same address. All the guides are at /guides; shorter answers are on the FAQ.