Why was my webhook flow deactivated?
At Atom, webhooks are essential for receiving and processing events from external platforms such as Meta. However, to ensure the correct functioning of the system and avoid mass errors, we have implemented an automatic webhook deactivation mechanism when critical and persistent failures are detected.
🛑 When is a webhook automatically deactivated?
A webhook may be automatically deactivated for any of the following reasons:
1,000 consecutive errors are detectedwhen trying to send data to the webhook.Example:the webhook is not receiving all the required parameters or returns an error every time Atom tries to send information.
1,000 consecutive errors are detectedwhen trying to send data to the webhook.
Example:the webhook is not receiving all the required parameters or returns an error every time Atom tries to send information.
Critical errors returned by Metathat interrupt normal operation.Examples:Rejected templatesEvent errorsSpam signalsExceeding the daily sending limit
Critical errors returned by Metathat interrupt normal operation.
Examples:
Rejected templates
Event errors
Spam signals
Exceeding the daily sending limit
📩 What happens when a webhook is deactivated?
If a webhook is automatically deactivated:
An automatic email is sent to the administrators of the company linked to the webhook, informing them of the deactivation.
An email is sent to our Development team so that the corresponding technical follow-up can be carried out.
✅ Recommendations
Regularly check the status of your webhooks.
Make sure the endpoints are active and responding correctly to the data sent.
In case of deactivation, review the errors received, correct the configuration and request the reactivation of the webhook, if necessary.