Rhinobird runs in the browser: AI Tools forms, Generate, credit displays, and History all depend on a stable session and network. When a page loads forever, buttons grey out, or previews never appear, the cause is often local—expired login, tab sleep, or extensions—rather than a lost generation. This article gives a practical order of checks so you recover quickly without duplicating credit spend, and so you know when to escalate true platform issues.
Confirm authentication state
Many features require an active account. If you see Login / Sign up, complete it with Continue with Google or Continue with Email, then navigate back to the tool you were using. Partial sign-in—cookie blocked mid-flow—can leave buttons visible but unresponsive. Sign out once and sign back in if the top bar shows inconsistent account info.
Separate slow loading from failed generation
- Initial page load slow — Large scripts or CDN latency; try one hard refresh, another browser, or a different network.
- Generate clicked, UI frozen — Job may still queue server-side; open History after a few minutes.
- Preview never appears — Distinguish processing time from error; read any toast on the tool page.
- Entire site unreachable — Check general connectivity before filing urgent tickets.
Browser hygiene checklist
- Update the browser to a current stable release.
- Disable ad blockers and privacy extensions temporarily for Rhinobird domains.
- Close duplicate tabs running the same long video job.
- Clear only site cache if you recently saw a blank form after deploy—avoid wiping all passwords unless needed.
- On laptops, prevent aggressive battery mode from throttling background tabs during long renders.
Corporate proxies and VPNs sometimes buffer uploads or websockets; a mobile hotspot test clarifies whether IT policy is involved.
Use History as source of truth
When the tool page spinner outlasts your patience, open History in the same signed-in session. Completed runs often appear there while the form still looks stuck. Download from History if preview is ready; return to the tool only to start your next brief. This avoids pressing Generate again purely because the UI lagged.
Credits display and unresponsive Generate
Generate shows expected credit cost when the form is valid. If cost never appears, required fields or uploads may be incomplete—scroll the form for validation hints. If cost appears but click does nothing, inspect browser console once for blocked requests, then retry after refresh. Insufficient credits may block runs; open account credit views or Pricing from the product chrome to top up before assuming a bug.
Long-running jobs vs broken UI
Video and large image batches legitimately take minutes. Do not chain ten identical jobs because the progress bar paused—check History first. If a job failed with system error, timeout, or no result, membership rules may return pre-deducted credits; verify credit transaction details before retrying. User-attributable failures need input fixes, not only refresh.
Escalate repeatable issues
Contact support when slowness persists across browsers, networks, and times of day, or when authenticated pages error consistently. Provide URL path (as text in your message, not as the only description), account email, browser version, and screenshots. Reach 13378452864 or support@rhinobird.ai. Legal and company context: Privacy Policy, Service Agreement, About Us.
Most “frozen” experiences are resync problems—sign-in, refresh, History—not lost work. Follow the checklist before you spend credits twice on the same brief.