Hookdeck work lives in the details of an event: its route, payload, destination response, retry history, and downstream consequence. Strawberry helps developers trace delivery failures, compare event patterns, prepare incident notes, and decide what deserves a controlled replay.
01
Find the delivery failures that are not merely retries.
A non-2xx response is not automatically a broken integration.
Compare destination, error class, retry outcome, and event type to identify the failures still preventing a business event from landing.
02
Trace one webhook from source to destination.
Debugging gets faster when the whole route is visible: what arrived, how it was transformed or routed, what the destination returned, and where the timeline first diverged.
03
Prepare a replay decision without duplicating business events.
Replaying a payload may create a second charge, ticket, notification, or record if downstream handling is not idempotent. Collect the delivery evidence and downstream state before proposing that action.
04
Review routes after the changes that can break them.
A route deserves a close check after destination releases, schema changes, or provider migrations, rather than on a vague generic schedule. Put those Hookdeck checks in a skill and have a routine assemble the relevant logs after each chosen release window.
Hookdeck Strawberry