Common failures
Delivery activity shows each attempt's response status, the start of your response body and the error. Most failures are one of these:
| What you see | Likely cause | What to do |
|---|---|---|
401 or 403 |
Your endpoint rejected our credentials: a wrong or expired bearer token, or an OAuth app missing its permission. | Check the subscription's authentication or OAuth connection. With OAuth we already retried once with a fresh token. |
3xx |
Your endpoint redirected. We don't follow redirects. | Use the final URL, including https:// and any trailing slash. |
404 or 405 |
The URL or path is wrong, or the endpoint doesn't accept POST. |
Check the endpoint URL on the subscription. |
5xx |
Your receiver failed while handling the event. | Check your receiver's logs for the X-Syncor-Delivery-Id. |
| Timeout | No response within 15 seconds. | Store the event and answer 2xx first, then process it. |
| Connection error | DNS, TLS certificate or firewall problem. | Check the hostname resolves publicly, the certificate is valid, and Syncor's servers can reach it. |
| Your receiver rejects the signature | The secret changed, or the body was parsed before it was checked. | Check the signature against the raw body, with the latest secret. See Authentication and signatures. |
| Subscription disabled | 20 failed attempts in a row. | Fix the cause, activate the subscription, then retry and resend (below). |
Recovering deliveries
- Send test event on a subscription sends a sample event of its type to your endpoint, signed and authenticated like a real one, so you can check your receiver end to end.
- Delivery activity lists every delivery with its status, attempts, response status, the start of your response body, the error and the next retry. Search by document number, PR number or event ID. Open a delivery to see each attempt and the body we sent.
- Retry a failed or stopped delivery, or Replay a delivered one, from Delivery activity. Both send the event with the same event ID and idempotency key, built with the subscription's current mapping.
- Resend events on a subscription sends the events of its type from a period you choose that were never sent to it, for example while it was paused or disabled, oldest first. It shows how many it will send before you confirm, never sends an event the subscription already received, and covers up to 500 events and 31 days at a time.
- Business events shows each event once, with its deliveries. Search by document number or PR number.
- API activity shows your calls to the Customer API, with the status, error code and request ID.
Retry, Replay and Resend events need the Integration Manager role and two-factor authentication on your portal account, and the subscription must be active.
Contacting Syncor support
Include the X-Syncor-Delivery-Id or the event ID, and the document number if you have it. For Customer API calls, include the request ID from API activity.