Overview

Use this guide to resolve common setup and integration issues quickly. Most problems are caused by configuration gaps, incorrect identifiers, or environment mismatches — all straightforward to fix once identified.

Assessment links not working

Symptoms: links fail to load or users cannot access the assessment.

Check:

• Was the correct deployment selected when generating the links?
• Have the links been modified or truncated when shared (e.g. a messaging app breaking the URL)?
• Has the session time limit expired? Links are only valid for the duration set in the Deployment Centre (default 24 hours from generation)

Fix: regenerate the links, test one yourself before distributing, and share via a method that preserves the full URL.

Assessment not completing / users dropping off

Symptoms: users start but do not finish; low completion rates in Beacon.

Common causes: poor network conditions, unclear instructions, device compatibility issues, or interruptions mid-session.

Fix:

• Provide clear instructions before sending users to the assessment — explain what it is and roughly how long it takes
• Encourage completion in one uninterrupted session on a stable connection
• Test across different device types to rule out compatibility issues
• Check drop-off patterns in Beacon to see where users are exiting

Results not appearing in Beacon

Symptoms: assessment completed but nothing shows in the results screen.

Check:

• Are you viewing the correct deployment in Beacon?
• Are you on the correct tab — Test or Production?
• Are any date range or status filters applied that might be hiding the result?
• Has enough time elapsed? Results typically appear within seconds but processing can occasionally take longer

Fix: search by UID directly, clear any filters, and confirm you're viewing the right deployment and environment.

Results not matching the correct user

Symptoms: results appear but cannot be matched to the expected user internally.

Cause: missing, incorrect, or duplicate UID passed when creating the session or generating the link.

Fix: audit how UIDs are assigned. Each session must use a unique value that maps to a record in your system. UIDs must be 5–60 alphanumeric characters and must not contain PII. If the same UID was used for multiple users, results will overwrite — use a prefix or suffix to differentiate.

Wrong deployment or environment used

Symptoms: assessments are running but results look wrong, or Test data appears in Production (or vice versa).

Fix: confirm the correct deployment is selected and that you are using the right Integration ID and API key for the intended environment. Test and Production credentials are completely separate — using the wrong one is one of the most common setup mistakes. Only Production data appears in the Beacon results screen.

API session creation failing

Symptoms: API returns an error when calling the session endpoint.

Also confirm you are not using Test credentials against a Production endpoint or vice versa. See Creating a Session for the full request reference.

Webhooks not receiving data

Symptoms: results are generated but nothing arrives at your endpoint.

Check:

• Is the webhook URL configured in Beacon → Deployment Centre → correct environment tab?
• Is the endpoint publicly accessible over HTTPS?
• Use the test API (POST /v1/webhooks-management/test) — a 503 means Begini cannot reach your endpoint; a 424 means no URL is configured

See Testing Webhooks for the full test API reference.

When to contact support

If you've worked through the above and the issue persists, contact Begini support via the Support Form in Beacon (profile dropdown → raise a support request). Include:

• The affected UID and integration ID
• Environment (Test or Production)
• Steps to reproduce
• Any error codes or response bodies

Next steps

• Creating a Session — API session creation reference
• Testing Webhooks — validate your webhook endpoint
• Webhook Troubleshooting — diagnose webhook delivery issues
• Operations Troubleshooting — broader operational issue guide