Where to start
CRM workspace → Tools → Britixo Automations (or Utilities in a classic layout)
Before you begin
Note the lead ID, the time the source action occurred, the Zap name and the expected destination result. Compare all times using a known timezone.
Follow these steps
- Check that the Zap is enabled and its app connection still passes a connection test.
- Ask an administrator to review the connector’s Active webhooks, Pending deliveries and Failed deliveries counters.
- Check Zap history for the event and then verify whether the destination action completed.
- Allow scheduled queue processing and any applicable backoff to run. If pending counts remain stuck, ask support to check the workspace scheduler.
- For failed or uncertain runs, give support the references and let them confirm the source and destination state before arranging a replay.
Check the result
A delivered event is distinguished from a completed business action. The destination result, not only a queue counter, confirms that the workflow achieved its purpose.
If something does not look right
A falling pending count can mean delivery, cancellation or terminal failure. If the expected destination result is missing, preserve the references and investigate both the connector and the Zap.
Fields, rules and limits
- The current worker processes up to 30 due deliveries per invocation.
- Successful HTTP 2xx receipt is recorded as delivered. That acknowledgement is not proof that all later Zap steps succeeded.
- Failures are attempted at most eight times. Backoff starts at about 60 seconds and grows up to one hour; scheduler timing and queue load add to the delay.
- There is no manual replay control on the current connector overview.
Questions and answers
Does delivered mean the email, spreadsheet or other action succeeded?
It means the webhook receiver acknowledged the event. Check Zap history and the destination app to verify later actions.
How soon should an event arrive?
There is no guaranteed delivery SLA in this module. Normal scheduling, queue depth, network conditions, retries and Zapier processing affect timing.
Why are pending deliveries not reducing?
The scheduler may not be running, jobs may be waiting for their next attempt, or the queue may be busy. Ask support to investigate with the recorded time and lead ID.
What does Failed deliveries mean?
A delivery reached a terminal failure state or failed destination validation. It needs investigation; repeatedly creating the same lead is not a recovery method.
Will an event wait forever?
No. The module has retry and retention limits. Escalate stuck or failed work promptly rather than treating the queue as a long-term archive.
Can I rely on delivery order?
No strict ordering guarantee is documented. Design downstream work to tolerate delayed or repeated events and verify the current record when order matters.
Does disabling a staff account affect queued events?
Yes. Authorisation is rechecked before delivery. Events whose subscription is no longer authorised can be cancelled.
Useful next steps
- Test and publish a Zap safely
- Prevent duplicate leads and automation loops
- Refresh or reconnect an expired connection
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.