Handle a failed QR integrity check | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/handle-a-failed-qr-integrity-check Publisher: Pixie Technologies LLC Troubleshooting and limitations Handle a failed QR integrity check Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Stop presentation of verified evidence and investigate the stored components. Audience: CRM staff; Permission: Administrator; Module v2.1.1; Where to goAdmin Area → QR Compliance Records → Open signed record Before you start - Use an authorised account and confirm the source CRM record or setting is correct. - Follow the exact route shown above; do not force database values to imitate a completed action. What this guide helps you do Stop presentation of verified evidence and investigate the stored components. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow. Follow these steps - Record the affected document and record ID. - Do not treat the PDF/public evidence as verified. - Check signature hash, snapshot fingerprint, HMAC and verification code. - Escalate unauthorised data changes through the security/audit process. Fields and options Action scopeStop presentation of verified evidence and investigate the stored components. Module version2.1.0 NavigationAdmin Area → QR Compliance Records → Open signed record EvidenceVerify the stored record, status, output, email, event or log produced by the code path. Rules and limits - Only values and transitions exposed by the supplied module code are supported. - Server-side validation remains authoritative even when browser controls appear to accept a value. Check it worked - The requested record, output or setting is created or updated through the supported module flow. - Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action. - An error message is investigated rather than bypassed. Security, privacy and operational checks - Apply least privilege and verify the correct customer, lead, sales document or recipient before processing. - Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy. - Test configuration changes with controlled records before production-wide use. - Retain or delete evidence only under an authorised retention process. Related guides QR Code Compliance module overview (https://pixiecrm.com/help-centre/qr-code-compliance-module-overview)Troubleshoot a missing verified QR stamp (https://pixiecrm.com/help-centre/troubleshoot-a-missing-verified-qr-stamp)Understand QR Code Compliance limitations (https://pixiecrm.com/help-centre/understand-qr-code-compliance-limitations)Export invoices and sales PDFs (https://pixiecrm.com/help-centre/export-invoices-and-sales-pdfs)Create a credit note (https://pixiecrm.com/help-centre/create-a-credit-note)