Troubleshooting
Every message below is quoted as the gallery actually returns it.
The search box
Section titled “The search box””Too many questions in a row — give it a minute.”
Section titled “”Too many questions in a row — give it a minute.””You have asked more than 20 questions in a minute from one address. Wait a minute. Nothing is wrong and nothing is lost.
”Search has used up today’s allowance and is resting until tomorrow — the filters below still work.”
Section titled “”Search has used up today’s allowance and is resting until tomorrow — the filters below still work.””The day’s model allowance is spent. This is not a rate limit and waiting a minute will not clear it — the allowance resets at 00:00 UTC.
Both of these arrive as a 429, so the sentence is how you tell them apart. The
filter rail, the dashboards, the permalinks and every download are unaffected;
see Limits and quotas.
”Search is unavailable at the moment. Try the filters instead.”
Section titled “”Search is unavailable at the moment. Try the filters instead.””The model call failed or ran past its 40-second ceiling. This one is worth retrying — the underlying cause is usually transient.
”keep it under 800 characters”
Section titled “”keep it under 800 characters””The question is too long. Questions are capped at 800 characters.
The answer says nothing matches, but I can see one that does
Section titled “The answer says nothing matches, but I can see one that does”Two things are worth checking before concluding the search is wrong:
- Ask with the words that are on the dashboard, including the metric. Chart titles and section headings are indexed, so “err-disabled ports” finds a dashboard whose own title never says it.
- Name the category. “switch related dashboards” is answered better by naming the Switching tag than by describing it — a dashboard can be about a subject without the word appearing in its text.
If it still does not surface, the fastest route is the filter rail: categories are exact where a search is a ranking.
I asked a follow-up and it did not understand
Section titled “I asked a follow-up and it did not understand”The search takes one question at a time and keeps no history — “and which of those is for switching?” has nothing to refer back to. Ask the whole question. This is deliberate and is explained in Ask about the dashboards.
The gallery
Section titled “The gallery”A filter link shows no dashboards
Section titled “A filter link shows no dashboards”Two different causes, and the rail distinguishes them:
- “Some filters in this link no longer exist:
d-sla.” The link names a category that has since been removed. Click Remove to drop just those and keep the rest of the selection. - “No dashboard carries every category selected.” Every category still exists, but nothing carries all of them at once. Selections are ANDed across kinds, so clearing one widens the results.
”There is no published dashboard at /d/…”
Section titled “”There is no published dashboard at /d/…””The slug does not name a currently published dashboard. It may never have existed, or it may have been unpublished — an unpublished dashboard serves nothing, including its images and its bundle, even though the files still exist in storage.
A dashboard image will not load
Section titled “A dashboard image will not load”Image URLs carry a revision number, and only the revision the record
currently points at is served. An older URL — from a cached page, or from
editing the number by hand — returns 404. Reload the gallery to pick up the
current one.
Downloads
Section titled “Downloads”The RUCKUS AI (SmartZone) button is greyed out
Section titled “The RUCKUS AI (SmartZone) button is greyed out”That platform has no export bundle yet, and the button carries the note
“Coming soon — the converter is being written”. Constructing the URL by hand
does not work around it: the route resolves the platform on the server and
answers 404. See
Download an export bundle.
”Too many downloads in a row — give it a minute.”
Section titled “”Too many downloads in a row — give it a minute.””More than 20 downloads in a minute from one address. Each download rewrites every identifier in the archive, so this bounds the work rather than your access — wait a minute and the same file is still there.
The download 404s
Section titled “The download 404s”The dashboard is not currently published, the platform is not available, or the slug does not exist.
Two people downloaded the same dashboard and got different files
Section titled “Two people downloaded the same dashboard and got different files”That is correct. Dashboard and chart identifiers are regenerated on every download, because an import matches objects by identifier and those identifiers match globally across tenants — two identical copies would collide, with the second import overwriting the first person’s dashboard. Dataset and database identifiers are the same in every copy, which is what binds the import to a real dataset.
An imported chart renders empty
Section titled “An imported chart renders empty”Check what the chart is filtered on. Filters pinned to tenant-scoped columns —
zoneName, ssid, apName and others — are removed from the bundle before
publishing, so a chart should render against your own data. A chart that comes
up empty anyway is usually one whose dataset does not exist in your tenant:
bundles reference datasets by identifier and do not contain them.
The imported dashboard still shows a venue or site name
Section titled “The imported dashboard still shows a venue or site name”In a chart title or a block of text, that is expected and is not a leak of
your data — it is a name from the original, which has no shape any pattern can
match. These are reviewed by a person before publishing rather than caught by a
rule. Values that do have a shape are replaced with documentation-range ones:
a 192.0.2.x address or a host-1.example.com hostname is a replacement, not a
real value. See
What is removed before publishing.
The request form
Section titled “The request form””That verification did not go through. Refresh the page and try again.”
Section titled “”That verification did not go through. Refresh the page and try again.””The bot check failed. A Turnstile token verifies exactly once and lasts five minutes, so the usual causes are a token that was already used or has expired. Refreshing the page is the reliable fix.
”Say a little more about what you want on it.”
Section titled “”Say a little more about what you want on it.””The description is under 10 characters. Naming the metric and who it is for is what makes a request buildable.
”Requests are closed at the moment. Try again later.”
Section titled “”Requests are closed at the moment. Try again later.””The bot check is not configured on the server, and the endpoint fails closed rather than accepting unverified submissions. There is nothing you can do from the page; contact support if it persists.
There is no request form anywhere
Section titled “There is no request form anywhere”The gallery hides the form entirely when the bot check is not configured, rather than showing one that cannot succeed.
The “already covered?” cards do not appear
Section titled “The “already covered?” cards do not appear”They need about 10 characters to start, and they show nothing at all on any failure — deliberately, since a duplicate check that blocks the form would have inverted its own purpose. The form still sends.
No clarifying question appeared
Section titled “No clarifying question appeared”It needs a draft of about 40 characters, and it is skipped when the day’s model allowance is spent. It is optional in every case — the request sends either way.