Resolve registration and verification problems
Recover safely from validation, delivery, missing-token, expired-link, network, and redirect failures.
Audience, roles, and scope
Covers errors exposed by the registration and verification pages without asking users to reveal token contents.
Who this is for
- Registrants who cannot complete email verification
- First-line support
Roles
- Public registrant
Before you begin
- The approximate registration time and time zone
- The masked destination address
- The displayed error category or message
Article tags
- registration problem
- expired verification link
- missing token
- verification failed
- email resend
Procedures
Follow the sequence and stop when identity, authorization, target, or result differs from the article.
Classify and recover the registration failure
Choose the least risky recovery based on the visible state.
- 1Identify the stage
Distinguish form validation, verification-email delivery, link verification, or onboarding redirect.
- 2Resolve form validation locally
Correct required name, email, organization length, address selection, and terms acceptance without injecting markup or control characters.
- 3Use controlled resend
After a successful form submission, wait for the countdown and use the provided resend action rather than submitting the entire form repeatedly.
- 4Restart after missing or expired token
Use Register again from the error page; do not reconstruct, edit, or paste token fragments.
- 5Retry a network error once
Confirm connectivity, avoid browser extensions that rewrite URLs, and retry after the service status is known.
- 6Escalate with sanitized evidence
Provide stage, time, browser, error text, and masked address while excluding every link token.
The registrant either restarts with a new controlled link or gives support enough non-secret evidence to investigate delivery or verification.
Security and data handling
- Use only the identity, tenant, role, and data scope approved for the task.
- Verify targets and expected effects before saving, sending, publishing, exporting, deleting, or approving.
- Keep secrets and regulated data out of screenshots, URLs, free-text diagnostics, and ordinary support messages.
Known limitations
- Support cannot safely validate a link from its token contents and should never request the complete URL.
- A verification link can expire or become invalid after use; the supported recovery is a new registration flow.
Troubleshooting
You cannot open Vianordis Registration
Likely cause: The session expired, the account is not entitled, or the required tenant or role claim is missing.
- Open the service through the approved Vianordis entry point and sign in again.
- Confirm the intended organization, tenant, and account are in use.
- If access remains denied, record the time and request an entitlement check; do not attempt direct-URL bypasses.
A documented control or navigation item is not visible
Likely cause: The current role, subscription, tenant configuration, release status, or feature flag does not expose it.
- Confirm the audience, role, prerequisites, and limitations in this article.
- Refresh after a new sign-in and verify the correct tenant context.
- Ask the responsible administrator whether the capability is enabled before reporting a defect.
A saved change or background result is not visible
Likely cause: Validation failed, processing is incomplete, the view is stale, or the feature is locally simulated rather than persisted.
- Review inline validation, status indicators, filters, and the selected tenant or workspace.
- Refresh once and search by a stable identifier before repeating the action.
- Do not repeat irreversible or externally visible actions until the first operation's state is known.
Source verification
Client validation, resend countdown and nonce, verification states, token expiry checks, and network-error handling.
Reviewed paths at 1fed26c
src/app/form/page.tsxsrc/app/verify/page.tsxsrc/app/api/register/route.tssrc/app/api/resend/route.tssrc/lib/token.ts
Contact support
Contact support when
- A repeatable Vianordis Registration error blocks an approved task
- Expected access, tenant scope, data, or status appears incorrect
- A security, privacy, financial, compliance, or data-loss concern is suspected
Include
- The page, action, expected result, and exact error text
- The time of occurrence with time zone and whether it is reproducible
- Your tenant, role, browser, and sanitized record or correlation identifier
- The troubleshooting steps already completed
Never include
- Passwords, access tokens, API keys, recovery codes, session cookies, or private keys
- Unredacted personal, financial, health, student, employee, or other regulated data
- Confidential documents or message bodies unless support provides an approved secure channel
- Any verification URL or fragment, resend nonce, or onboarding token