Build a useful investigation brief
Build topic fixtures
Create one supported topic, an omitted topic, a renamed label, an unexpected topic, and two topics with similar payload shape. Record expected subscription, branch, acknowledgement, and state before execution. Keep the subscription revision with each fixture.
Trace configuration to state
Capture subscription settings, endpoint, topic header, event ID, schema or version, route branch, receipt, and workflow result. Compare the first divergence between configured and observed topic. Keep source and delivery identity separate.
Vary one coverage input
Change only topic, filter, subscription revision, schema version, or handler branch. Compare delivery and state. If a missing event could be sender filtering or receiver routing, name the source evidence needed to distinguish them.
What to carry forward
The investigation is ready when fixtures show configured topic, delivered header, branch, receipt, and workflow effect. Deliver a narrow subscription or route change. Keep unsupported topic and sender filter behavior explicit where unobserved. Keep route and subscription evidence together for every fixture.
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