🔌 Why was my webhook flow deactivated?
In Atom, webhooks are essential for receiving and processing events from external platforms like Meta. However, to ensure the correct functioning of the system and avoid massive errors, we implement an automatic webhook deactivation mechanism when critical and persistent failures are detected.
🛑 When is a webhook automatically deactivated?
A webhook can be automatically deactivated for any of the following reasons:
1000 consecutive errors are detected when trying to send data to the webhook.Example: The webhook is not receiving all the required parameters or responds with an error every time Atom tries to send it information.
1000 consecutive errors are detected when trying to send data to the webhook.
Example: The webhook is not receiving all the required parameters or responds with an error every time Atom tries to send it information.
Critical errors returned by Metathat interrupt normal operation.Examples:Rejected templates.Event errors.Spam signals.Exceeding 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?
In case a webhook is automatically deactivated:
An automatic email is sent to the administrators of the companylinked to the webhook, informing them of the deactivation.
An email is sent to our Development team, so they can do the corresponding technical follow-up.
✅ Recommendations
Regularly check the status of your webhooks.
Make sure the endpoints are active and respond correctly to the data sent.
In case of deactivation, review the errors received, correct the configuration and request the reactivation of the webhook if applicable.