Retries and troubleshooting

مهلة الاستجابة وجدول إعادة المحاولة وحالات صحة الويب هوك في زد، وما تفحصه عندما تتوقف الطلبات عن الوصول.

Timeouts and retries

	Salla	Zid
Timeout	About 30 seconds to connect and respond	Not documented
Retries	3, about 5 minutes apart	3, after 1, 5 and 15 minutes
Counts as failure	No successful response	Non-2xx response, timeout or connection error
After repeated failures	Not documented	The webhook is marked degraded, then broken (below)

Sources: Salla Webhooks, Zid Webhook Health Tracking.

Zid webhook health

Zid counts failed deliveries per webhook over a sliding 60-minute window:

• 10 or more failures: the webhook becomes degraded.
• 30 or more failures: it becomes broken. Zid stops sending to it, drops pending events, and emails you a CSV of broken webhooks (subject: "Action Required: Your webhook endpoints are failing").
• Any successful delivery resets the count and returns it to healthy.

A broken webhook stays broken until you recover it through the API, with a new target URL. The Health Summary, Broken Webhooks and Recover Broken Webhooks endpoints cover this.

Webhooks aren't arriving

1. Check the subscription exists. Salla: List Active Webhooks. Zid: List Webhooks, and the health summary above.
2. Check scopes. On Salla the app needs the webhooks read/write scope, plus read access to the resource (orders, products and so on).
3. Point the webhook at a request bin such as webhook.site and trigger the event in a development store. If it arrives there, the problem is your server.
4. Check the event name. Names differ between the platforms (order.created on Salla, order.create on Zid) and some Salla names don't follow the pattern (abandoned.cart, review.added, specialoffer.created).

Signature checks keep failing (Salla)

• You're hashing parsed-and-reserialised JSON instead of the raw body. See Verifying requests.
• The secret is from a different app, or from before you regenerated it.
• The webhook uses the Token strategy, not Signature. Check X-Salla-Security-Strategy.

The payload doesn't match these docs

These pages are generated from the platforms' published schemas and examples, which are sometimes behind what is actually sent. Log the raw body you receive, and open an issue with the event name and the difference (remove customer data first).