Customer work, connected.

Help & supportMyAccount
Troubleshooting and limitations

Troubleshoot a missing verified QR stamp

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Separate pending status, disabled stamp, integrity failure and placement causes.

Audience: CRM staffPermission: Staff loginModule v2.1.1
Jump to steps
Where to goAdmin Area → QR Compliance Records → record, then source document → PDF
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

Separate pending status, disabled stamp, integrity failure and placement causes. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Verify the record is signed.
  2. Verify integrity PASS.
  3. Enable Verified stamp.
  4. Check automatic or complete manual coordinates.
  5. Regenerate the PDF.

Fields and options

Action scopeSeparate pending status, disabled stamp, integrity failure and placement causes.
Module version2.1.0
NavigationAdmin Area → QR Compliance Records → record, then source document → PDF
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.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page