™2 min read
Track from your side
Log every received event id and its outcome. A sudden gap in ids or a spike in handler errors is your earliest signal.
Alert on failure runs
Alert if your handler returns non-2xx repeatedly, or if you stop receiving expected event types. Fix inside the 72-hour retry window and no events are lost.
Know the disable threshold
Seven consecutive days of all-failed deliveries disables the endpoint. Re-enable it once healthy; events still inside their retention are delivered.
Frequently asked questions
How will I know if my endpoint was disabled?
The partner dashboard flags a disabled endpoint. Monitoring delivery success your side catches it far sooner — before the 7-day threshold.
Do disabled endpoints lose events permanently?
Events past the 72-hour retry window are gone from the queue. Re-enable promptly and reconcile older gaps by re-reading the API.
What signals should I watch?
Three: the rate of non-2xx responses from your handler, gaps in the sequence of event ids you receive, and the age of the newest event of each expected type. A spike in the first, or a stall in the third, is your cue to investigate before the auto-disable threshold is anywhere near.
Funding for UK limited companies
Credicorp lends to your company, not to you personally — short-term working capital with no personal guarantee. See what your business could access.