A webhook was turned off
Why a lead box gets disabled, what the email means, and how to get it running again.
What happened
Every event a lead box sends is retried up to 18 times over about four days when your endpoint does not answer with a 2xx. When the last retry fails, Mav turns the lead box off and emails your account's admins and managers. The subject is Lead Box "name" has been disabled. Events that happen while it is off are not queued; they are gone.
Find the cause
Check your endpoint for the days before the email:
- Timeouts. Mav waits 3 seconds to connect and 3 seconds for a reply. Reply
200first and do the work afterwards. - Redirects. A
301or302counts as a failure. Point the lead box at the final URL. - Auth. If your endpoint expects a token, set Auth to Bearer on the lead box and enter it.
- A changed URL after a deploy or a vendor migration.
Get it running again
Fix the endpoint, then create a new lead box with the same agents, events and delivery, and use Send test to confirm a 2xx before you rely on it. A disabled lead box cannot be switched back on from the app today, and removing the old one is a Mav admin task, so tell your Mav contact and they will clear it up.
Check before it happens
Send test on any lead box posts one sample event right away and shows the result as a toast, so you can verify a new endpoint in seconds.
Still have a question?
Our team answers in the thread. Ask us anything about your account.