Delivery status and retries
Track Qubeforms email and webhook delivery status after submission. Understand asynchronous processing, retry attempts, priority queues, and failed or canceled delivery.
1. Separate receipt from delivery
A successful form submission means Qubeforms received the record. Notification email, autoresponders, and webhooks are processed asynchronously and can arrive later. Open the submission detail to inspect delivery records, or use the read API’s deliveries array. Each destination/channel has its own status. One destination can succeed while another retries. Spam submissions do not schedule normal deliveries.
2. Read the delivery status
pending means a delivery is waiting to be queued; queued means it was handed to the worker; sending means a worker is attempting it. retry means another attempt is scheduled after a failure. delivered means the email transport or webhook endpoint accepted the send; it does not prove that a person read it or that your receiver completed downstream business work. failed means the configured attempt limit was reached. cancelled means current eligibility checks stopped the send.
3. Understand retry timing
The default maximum is 6 send attempts. After successive failures, the default delays before remaining attempts are approximately 60, 120, 240, 480, and 960 seconds, plus queue and scheduler time. A successful destination is not deliberately resent because another destination failed, but network uncertainty can still cause duplicate delivery. Webhook receivers should deduplicate by submission ID. Retry timing is not a guaranteed delivery deadline.
4. Understand priority delivery
Pro and Business use the priority delivery queue. When both queues have work, the default dispatcher reserves 75 percent of each batch for priority work while continuing to serve standard deliveries. This changes scheduling preference, not the receiver’s response time or a guaranteed arrival time. Starter notifications, autoresponders, and webhooks use the standard queue. Routing-rule priority is a separate rule-order setting.
5. Investigate failures or cancellations
Check the last error and attempt count. For email, confirm that the recipient is still verified, within the current plan limit, and able to receive mail. For autoresponders, confirm the feature and paid entitlement remain active. For webhooks, verify the public HTTPS destination, signature handling, response time, and 2xx response. Queued deliveries can be cancelled if the form is no longer active, a recipient becomes ineligible, the plan changes, or the webhook endpoint is replaced.
6. Escalate stalled deliveries
If records stay pending or queued, or all channels stop advancing, contact support with the form ID, submission ID, channel, and approximate time. The scheduler and queue workers must be running for delivery to progress. The customer dashboard does not provide a manual retry button; ask the operator to investigate exhausted attempts rather than repeatedly submitting the same visitor data. Do not include secrets or private download links in a support message.
Public form keys can appear in browser code. Read keys, management credentials, and webhook signing secrets must stay on the server.