Aglet

Triage webhook subscription topic drift

A topic change can add unexpected work or silently remove a needed event. Freeze one coverage gap and record subscription, environment, observed topic, handler branch, and resource result. Separate a deliberate rename, filter omission, version change, and obsolete route label.

Establish what is happening

  1. Capture configured coverage

    Record endpoint, environment, configured topics or filters, subscription revision, observed topic, event ID, and route result. Protect payload data and secrets. Note the last known delivery for a topic that may have disappeared.

  2. Compare topic to branch

    Run a supported topic, an omitted topic, a renamed topic, and an unexpected topic through a safe receiver. Compare headers, parser, branch, acknowledgement, and resulting state. A valid payload shape does not prove the subscription selected it.

  3. Bound workflow gaps

    Group changes by topic, subscription, endpoint, schema version, handler revision, and affected workflow. Separate missing delivery, wrong branch, unsupported topic, and duplicate coverage. Preserve resources whose state depends on the missing event.

What to carry forward

Triage ends with configured and observed topic, first coverage boundary, affected workflow, and evidence gap. Hold broad subscription edits. Route configuration, schema, and handler questions separately. Name the first record a reviewer must obtain and keep the missing workflow state visible.

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