Maintained answers · Troubleshooting and operations
Find the right evidence before changing configuration or code.
Questions and answers
Product behavior, requirements, pricing, and integrations can change. The contextual link in each answer is the maintained next step.
Answer 01
Direct linkCheck lighting, screen brightness, the full code, camera permission, HTTPS, and the scanner keyboard layout. Staff can use a phone camera, fixed 2D reader, customer search, or a known member code as the documented fallback.
Use the staff scanning guide for the complete decision path.
Answer 02
Direct linkCheck the configured mail service, sender identity, credentials, domain authentication, queue or scheduled work where relevant, application logs, provider response, spam placement, and the member’s email preferences for the message type.
Start with email configuration and the health center.
Answer 03
Direct linkStop repeated production attempts. Preserve the error and logs, confirm the backup, review requirements and release notes, reproduce the update on staging, and check custom source changes and file permissions.
Use the updating guide and contact support with the license key, release, environment details, exact error, and steps already tried.
Other answer topics
Open the cluster that matches the next decision instead of stretching one answer beyond its evidence.
Pick what runs. Your choice is stored on this device for 12 months and you can change it any time through Cookie settings in the footer.
Necessary
Session and security cookies (reward-loyalty-session, XSRF-TOKEN). Forms and sign-in break without them.
Analytics
Google Analytics counts visits and shows which pages work. Sets _ga cookies for two years.
Every cookie, purpose, and retention period: cookie policy.