Troubleshoot a Bilty that will not issue | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/troubleshoot-a-bilty-that-will-not-issue Publisher: Pixie Technologies LLC Administration, security and troubleshooting (https://pixiecrm.com/help-centre/topic/bilty-administration-troubleshooting) · How-to guide Troubleshoot a Bilty that will not issue Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Use the missing-requirements list, Fix It controls, permissions and record state to resolve issue blockers without bypassing validation. The guide follows the Help Centre standard: exact route, prerequisites, ordered steps, verification and operational boundaries. Audience: Administrators and authorised Bilty operations staff; Permission: Relevant Bilty Management capability; Module v1.0.0; Where to goBilty Management → Dashboard → Issue Bilty Before you startRequired access: Relevant Bilty Management capability. Work on the correct tenant and record. Use least privilege and review any dependency or protected workflow warning before continuing. What this guide helps you do Use the missing-requirements list, Fix It controls, permissions and record state to resolve issue blockers without bypassing validation. Bilty Management keeps drafts, issued records, public capability links, finance, integration events and audit evidence as connected but separately verifiable records. How it works Configure tenant controls, preserve protected invariants and troubleshoot production workflows. Use the module's current status, permission checks, warnings and linked records to decide the next supported action. Where a downstream invoice, WhatsApp queue item, webhook, PDF, POD record or audit event applies, verify it separately. Follow these steps - Go to Bilty Management → Dashboard → Issue Bilty and reproduce the issue on the intended tenant and record. - Read the exact warning, validation response, lock state, integration diagnostic or status before changing anything. - Check the inputs and dependency relevant to this problem: Use the missing-requirements list, Fix It controls, permissions and record state to resolve issue blockers without bypassing validation. - Correct the smallest supported cause; do not bypass permissions, protected validation or security controls. - Retry once, then reopen the record and confirm the stored state and audit evidence. Settings to check DependenciesDependent options fail safely when public verification or e-sign is disabled. Protected rulesPrivacy, auth, Cash-only finance, signature integrity and audit integrity cannot be switched off. CronModule cron expires stale locks, processes webhook queue and purges old API request logs. Production boundaryLive connector/network delivery must be verified in the actual staged environment. Record, audit and evidence checks Reopen the relevant Bilty record or register and confirm its identifier, current status, related parties, timestamps and connected evidence. Check the audit/compliance, payment, public-link, report, API, webhook or WhatsApp evidence that applies to this workflow rather than relying only on a success alert. Check it worked Return to Bilty Management → Dashboard → Issue Bilty or the resulting register and verify that the stored state matches the intended action. For any downstream automation, confirm the downstream record or queue/log entry as a separate completion check. Technical basis for this guidance This guide was checked against views/admin/settings.php; bilty_management.php; controllers/Bilty_management.php; models/Bilty_management_model.php; docs/VALIDATION_REPORT.txt. It documents only behaviour exposed or enforced by the supplied module; internal secrets, raw signature payloads and unsupported future workflow assumptions are intentionally excluded. Common mistakes to avoid - Work only on the intended tenant and Bilty record. - Do not bypass a missing permission, validation blocker or protected status by changing unrelated settings. - Verify the stored record, downstream integration state and audit evidence after any material action. Data and workflow safetyConfirm the exact Bilty, authorised audience and final stored status before issuing, publishing a link, recording payment, changing shipment state or sharing a document. Browse connected topics:administration, security and troubleshooting (https://pixiecrm.com/help-centre/topic/bilty-administration-troubleshooting)bilty management (https://pixiecrm.com/help-centre/category/bilty-management) Related guides Configure public verification security limits (https://pixiecrm.com/help-centre/configure-public-verification-security-limits)Review the Bilty Administration and Configuration Centre (https://pixiecrm.com/help-centre/review-the-bilty-administration-and-configuration-centre)Understand protected non-configurable Bilty security rules (https://pixiecrm.com/help-centre/understand-protected-non-configurable-bilty-security-rules)