Aglet

Verify webhook subscription topic coverage

Topic verification must check both presence and disposition. Exercise every supported topic, one omitted or renamed label, an unexpected topic, and overlapping payload shapes. Inspect acknowledgement, identity, handler branch, and workflow state rather than only delivery count. Check this before accepting the subscription change.

Check whether the outcome improved

  1. Define topic outcomes

    Write expected subscription, header, parser, branch, acknowledgement, review, and workflow result for supported, omitted, renamed, unexpected, and overlapping topics. State which topics remain unsupported. Keep the observed header beside the expected route.

  2. Run coverage fixtures

    Send synthetic events through each subscription and compare configured filter, observed topic, schema, route, receipt, and state. Confirm a required topic is not swallowed by a filter and an unsupported one does not trigger a side effect.

  3. Check updates and replay

    Change one topic or filter, then process a duplicate and a previously missing event through the approved path. Verify event identity, route, and state remain safe. Keep payload contents bounded in diagnostics.

What to carry forward

Accept when supported topics reach the intended branch, unsupported ones have a visible disposition, and subscription changes preserve workflow coverage. Keep sender filtering partial when uncontrolled. Record topic matrix, revision, fixtures, and results. Keep omitted topics from becoming silent gaps.

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