Overview
Every time a webhook fires, Mobaro records the delivery — the attempt to send that event to your endpoint. The delivery log lets you confirm what was sent, see which deliveries succeeded or failed, and retry a failed one once your endpoint is back. It's the difference between hoping an integration is working and being able to prove it.
Availability: Webhooks are an early-access feature. If you don't see Webhooks in your environment, contact Mobaro Support to enable them.
Why this matters: Endpoints go down, deploys happen, networks blip. Without a delivery record, a missed event is gone until the source record changes again. With one, you can see exactly what failed and re-send it — so a brief outage on your side doesn't turn into missing data.
The delivery log
The delivery log lists the webhook events Mobaro has attempted to send, most recent first. Each entry ties an event (a resource plus Created/Updated/Deleted) to its delivery outcome, so you can tell at a glance whether your endpoint received it.
Note: A successful delivery means your endpoint accepted the request (a 2xx response). A failed delivery means it didn't — your endpoint was unreachable, returned an error, or took too long to respond.
Retrying a failed delivery
When a delivery fails because your endpoint was briefly unavailable, you don't have to wait for the underlying record to change again to get the event. Find the failed delivery in the log and retry it — Mobaro re-sends the same event to the same URL.
Best practice: Fix the endpoint first, then retry. Retrying while the endpoint is still down just produces another failed delivery. If many deliveries failed during an outage, bring the endpoint back, confirm it's healthy with one retry, then work through the rest.
Heads-up: A retry re-sends the same event, so your endpoint may receive an event it has already processed. Make your processing idempotent — keyed on the payload's objectId and timestamp — so a repeat delivery doesn't cause duplicate downstream actions.
Removing a delivery record
You can remove a delivery record from the log once you no longer need it — for example after clearing out the noise from a resolved outage. Removing a record only deletes the log entry; it has no effect on the source data in Mobaro or on anything your endpoint already received.
How this relates to endpoint-side handling
There are two sides to reliable webhooks:
Mobaro's side (this article) — the delivery log and manual retry, for seeing and re-sending what Mobaro attempted.
Your endpoint's side — responding quickly, returning a 2xx, and processing idempotently. See Handling errors, rate limits, and retry logic.
For webhook setup and the payload shape, see Using webhooks in Mobaro.
Frequently asked questions
Q: What counts as a failed delivery?
A: Any attempt your endpoint didn't accept with a success (2xx) response — it was unreachable, returned an error status, or responded too slowly.
Q: Does retrying change the payload?
A: No. A retry re-sends the same event for the same object. Because it can arrive more than once, keep your processing idempotent.
Q: If I disable a webhook, what happens to events during that time?
A: A disabled webhook doesn't send, so there are no deliveries to retry for that period. Re-enable it to resume sending future events. See Using webhooks in Mobaro.
Q: Does removing a delivery record delete any data?
A: No. It only removes the log entry. The source record in Mobaro and anything your endpoint already received are unaffected.