Aglet

Prioritize webhook response policy failures

Response policy should queue by what the status causes, not by status number alone. A retried invalid event and a discarded transient failure fail in opposite directions. Weigh effect state, shared handler reach, sender behavior evidence, and recovery cost in the shared handler.

Decide where the work belongs

  1. Map status consequence

    For each response, record event identity, operation, status, receipt, side effect, retry, and current state. Separate before-receipt rejection from after-receipt duplicate. Keep the decision table tied to actual handler branches.

  2. Compare containment

    Assess correcting one status, retaining the event, pausing a route, reviewing a duplicate, or using an existing retry path. Record authority and backlog impact. Do not make every failure transient to improve delivery counts.

  3. Set policy order

    Queue statuses that can lose recoverable events or repeat effects, then shared mapping changes and display-only diagnostics. Set owner, fixtures, review time, and evidence threshold. Keep sender interpretation provisional without delivery evidence.

What to carry forward

Return a status queue with intended disposition, effect and retry consequence, endpoint reach, owner, and proof needed to reprioritize. Escalate loss and duplicate amplification. Keep ranking provisional where sender behavior is unknown. Name the sender disposition that makes each status consequential, including discarded events and retries that can repeat an already completed effect.

Technical background: Zendesk developer documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow