Skip to main content
This page collects real issues found and verified while building this documentation — plan-quota gaps, UI bugs, and genuinely confusing flows — each pointing to the specific page that covers it. It isn’t a generic troubleshooting checklist; every entry below was actually reproduced against the live app.

​
Account & sign-in

See Multi-factor authentication for how backup codes work, and save them the moment you enroll a method. If you’ve lost both your MFA method and your backup codes, this documentation project itself hit that exact wall on a shared test account partway through verification — there is no in-app self-recovery path once both are gone; contact Support directly.
Use Password reset from the login screen. This is separate from MFA recovery codes — losing your password doesn’t affect your MFA enrollment, and vice versa.
That’s expected, not a bug — Multi-factor authentication only applies to password-based sign-in. If your organization signs in through SSO, your identity provider handles that layer instead, and Scanova doesn’t manage it.

​
QR codes and scanning

Open QR Health Center (/qr/health) before checking codes one by one — it surfaces unpublished drafts, expired schedules, broken form links, and incomplete domain verification across your whole account in one place.
This is a fundamental, upfront choice, not a setting you can change after creation for every type. See Quick Code vs. full Page for exactly which types are “Dynamic” (editable after publish) versus “Static” (fixed at creation).
A real bug was found during this documentation project: reopening the Configure location modal in GPS geofencing can crash in development due to a missing translation key. If you hit this, refresh the page — your saved location, range, and fallback settings are not lost; they’re stored independently of the modal.

​
Folders, tags, and team permissions

This is very likely a plan-quota gap, not a bug on your end. Folders, tags & bulk operations confirms the folder sidebar is plan-gated (FOLDER_MANAGEMENT) — and during this documentation project, that quota was found granted to exactly one plan in the entire database (an internal-only plan). If you’re on a paid plan and expect folders, contact Support — you likely aren’t the only one missing it.
Both require a separate permission grant (FOLDER_CAN_CREATE_AND_MANAGE) on top of the plan quota above. A shared user without that specific permission won’t see those controls at all — ask your account owner to grant it. See Folders, tags & bulk operations.
This isn’t a bug — Lead Lists are a legacy feature. Scanova no longer exposes a way to create one from the app; new lead capture goes through Forms instead. See Leads & lead lists for what you can still do with existing lists (view, export).

​
AI Studio and API access

A real product gap, not a docs issue: verifying AI Studio during this project found that the canonical Pro plan doesn’t actually grant the AI_QR_TOKENS quota the app checks — so a genuine, paying Pro customer can hit this paywall. See AI QR / AI Studio for the exact wording shown. If this happens to you, check your plan’s feature list or contact support rather than assuming your account is misconfigured.
Management API access is also plan-gated (MANAGEMENT_API), and — like the AI Studio and Folders gaps above — this quota was found missing from the canonical Pro plan during verification. See Creating & managing API keys for where the limit is shown in the UI.
There currently isn’t one — this was confirmed live, not assumed. See API usage dashboard for exactly what was checked and which endpoints to call directly in the meantime.

​
Switching between Classic and New Scanova

This is expected, one-way behavior, not a bug — see Switching from Classic to New UI for the corrected explanation. A page built in New Scanova keeps working live but becomes permanently read-only once viewed from Classic; there’s no in-app undo.
Also expected — switching platform is an account-wide decision only the account owner can make. Ask them to switch it from their own account.
  • FAQ — shorter, single-answer questions that didn’t need a full walkthrough.
  • Support — live chat, WhatsApp, and phone numbers if nothing above resolves it.