Aglet

Prioritize redirected webhook delivery risk

A redirect during a planned host move differs from a redirect to an unknown destination. Prioritize trust and lost-event risk, then shared endpoint impact. Keep a redirect-following workaround behind proof that method, body, signature, and destination remain acceptable before changing destination policy.

Decide where the work belongs

  1. Map destination risk

    For each endpoint, record origin, target, method, body handling, signature result, receipt, and event effect. Separate direct canonical delivery from a redirect that changes trust or loses the body. Keep real endpoint labels with each item.

  2. Compare migration paths

    Assess updating configuration to a canonical URL, retaining a reviewed proxy, pausing delivery, or reviewing a bounded resend. Record ownership and rollback. Do not permit arbitrary redirect targets merely to recover a backlog.

  3. Set redirect order

    Queue unknown destinations, changed methods or bodies, and pre-receipt loss first. Set owner, fixture, review time, and acceptance evidence. Keep a harmless temporary hop below a shared signature or tenant-routing risk.

What to carry forward

Return a redirect queue with destination, trust and effect risk, receipt evidence, containment, owner, and migration proof. Escalate unapproved targets. Keep rank provisional when sender redirect behavior cannot be observed. Keep destination trust ahead of delivery volume. Name the migration owner.

Technical background: Stripe 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