Knowing When an Integration Stops: Webhook and Connector Failure Alerts in Carriyo
On Wednesday we wrote about the integrations nobody is watching before Black Friday, and how a webhook or connector can stop working without anyone noticing until customers start asking where their orders are. Two of the things we suggested were having alerts on failure rather than on complaints, and making sure those alerts reach someone at a sensible pace. In Carriyo's release last week, 2026.10-R7 on 15 October, we added both of these for the webhooks and connectors that run through Carriyo, along with a 30-day activity log on every webhook and connector.
The same release also brings combined shipping documents, which we think will help at packing stations over peak, so we cover that at the end.
What Carriyo already did when a webhook failed
It is probably worth starting with what was already there, because the new alerts sit on top of it. When a webhook delivery from Carriyo fails, because the receiving system returns an error, times out or cannot be reached, Carriyo retries it on a fixed schedule. By default that is three retries over about eight minutes, and if extended retries are switched on for that webhook, Carriyo keeps trying for about 30 hours. Once the retries are used up the event stays in the Integration Monitor, where someone can re-send one event or a batch of events that failed during an outage, and the same can be done through the API.
That covers short blips well. What it did not do was tell anyone. If a receiving system was down for a day, the failed events were all there in the monitor, but someone had to think to go and look.
Webhook Failure and Connector Failure alerts
There are now two new alert events, which you switch on in Settings > Account > Alerts.
- Webhook Failure is raised when deliveries to one of your webhooks fail, and resolved when that webhook succeeds again.
- Connector Failure is raised when requests between Carriyo and a connected platform fail, and resolved when the connector succeeds again. Requests made from the Carriyo dashboard or the API don't count towards it.
Carriyo checks each webhook and each connector every hour. One alert covers one run of failures, so if a webhook keeps failing over several hours, the later hours are added to the same alert rather than opening a new one each time. On the Alerts Dashboard, a failure alert shows which webhook or connector it is, its failed deliveries, and the times of the first and last failure. VIEW opens the failed activity for that webhook or connector, so you can go straight from the alert to the requests that failed. The alerts are shown to users who are able to retrigger webhooks.
Alert emails at the pace that suits you
Until this release, alert emails always went out hourly. In your alert settings you can now choose to receive them every hour, every 6 hours or once a day, and each email lists the open alerts raised since the previous one. For a team with someone on call over the Black Friday weekend, hourly probably makes sense, while a team that reviews things each morning may prefer one email a day that it actually reads.
The Alerts Dashboard also has a new shipment type filter, so you can look at alerts for forward shipments and reverse shipments separately, which is useful as returns start to build after peak.
A 30-day Activity tab on every webhook and connector
Webhooks and connectors in Settings > Integration now open on a read-only page, and you click Edit to change them, which we think makes it less likely that someone changes a live connection by accident in the middle of a busy week. There is a new Activity tab that lists the last 30 days of requests.
- For webhooks, it shows each delivery attempt with its response code, the time it took, the trigger and the entity it was about. Show all attempts lists every attempt for one delivery, so you can see the retries in order.
- For connectors, it shows each operation with its status, the operation, its source and, where something failed, the failure reason.
You can filter by success or failure and open any entry to see the request and response. Activity logs here and in the Integration Monitor now mask secret values in headers, URLs and query parameters. A header whose name contains words such as authorization, token, secret, password or signature shows as asterisks, plus the last four characters for a longer value, so people can troubleshoot a connection without seeing the credentials behind it.
In the Integration Monitor, a custom time period for webhooks or connectors can cover at most 31 days, and webhook and connector event history is kept for one year.
Combined shipping documents for the packing station
The second part of the release is smaller but probably quite welcome in a busy warehouse. A combined document merges several of a shipment's PDF documents into one file, so a packer can print everything a parcel needs in one go instead of opening and printing documents one at a time.
You set it up in Settings > Administration > Documents by adding a document with Combined as its type, choosing the shipment type and picking two or more documents to combine. The PDF follows the order you pick them in. You can combine the Carriyo PDF label, the carrier PDF label, the carrier commercial invoice and your active shipment documents, whether they are generated or uploaded. Carriyo adds the combined document to a shipment once every document in it is on the shipment, and a combined document that includes the commercial invoice is only published for cross-border shipments, because domestic shipments don't have one.
For systems that print automatically, shipment webhooks have a new trigger, Combined Document is generated, which fires when the combined document is added to a shipment. The document appears in the shipment's documents with the type combined, and its link builds the PDF each time it is opened.
Why we think this matters more than the feature itself
Connecting to a platform or a carrier is the part people tend to see. We connect to 140+ carriers and to commerce platforms such as Shopify, Salesforce Commerce Cloud, Magento and Mirakl, but in our experience the harder and more valuable part is running those connections for years, through API changes, expired credentials, outages on either side and peak volumes, and knowing quickly when one of them stops. A lot of that know-how sits in work like retries, replays, masking and now alerting, which nobody notices when it works.
We say this partly because more teams are now building pieces of their commerce stack in-house, often with AI doing much of the coding, which makes sense for a lot of things. From what we have seen, though, monitoring is usually the part that gets left for later in an in-house build, and peak is not a great time to find that out. Having it handled as part of the platform is one less thing for your own team to build and watch.
Switching it on
If you're a Carriyo customer, the two alert events are in Settings > Account > Alerts, and the email frequency is in your alert settings. The full detail of the release is in the 2026.10-R7 release notes. If you would like to talk through how your integrations are set up before peak, or what moving them onto Carriyo would look like, you can talk to us.
Carriyo is The Intelligent Commerce Platform, from checkout to doorstep.
---
Sources
1. Carriyo. "Before Black Friday, Check the Integrations Nobody Is Watching" (Carriyo blog, October 2026). https://carriyo.com/blog/black-friday-check-integrations-nobody-2026-10-21/ 2. Carriyo. "Release 2026.10-R7" (Carriyo changelog, 15 October 2026). https://carriyo.com/docs/changelog/2026.10-R7 3. Carriyo. "Retry and idempotency" (Carriyo webhooks documentation). https://carriyo.com/docs/platform/webhooks/retry-and-idempotency/ 4. Carriyo. Connectors documentation. https://carriyo.com/docs/connectors/ 5. Carriyo. Carrier network. https://carriyo.com/carriers