Troubleshooting
No certificate was issued for an order
Issuance stops for one of six reasons. The most common after a settings change is that your trigger is fulfillment, not payment.
Issuance stops for one of six specific reasons, and they are checked in this order. Working down the list resolves almost every case.
- Auto-issue is switched off. With auto-issue paused, orders are ignored entirely and nothing is recorded against them. The dashboard states plainly whether auto-issue is on, so check there first.
- The order has not hit your chosen trigger yet. You choose whether certificates are issued when an order is paid or when it is fulfilled. If your trigger is set to fulfilled, a paid-but-unfulfilled order correctly issues nothing. This is the single most common "it stopped working" report after a settings change.
- The order had no eligible line items. Gift cards are skipped by design, so an order containing only gift cards issues nothing.
- Tag opt-in is on and the products do not carry the tag. If you have limited issuance to tagged products, only products carrying your opt-in tag are certified. Check the tag on the product matches exactly, including hyphens and case.
- You have reached this month's certificate allowance. Each plan includes a monthly allowance, and once it is used, further certificates are skipped rather than queued. The counter resets at the start of your next billing period. The app records these as skipped for quota, so you can see exactly how many were affected.
- The certificate already exists. Certificates are unique per physical unit, so a redelivered or replayed webhook returns the existing certificate instead of issuing a duplicate. Two of the same item on one order correctly produce two certificates, not one.
Related articles