Check whether the outcome improved
Define routing outcomes
Write expected tenant, resource, authorization, route, receipt, review, and effect for valid, missing, conflicting, similar-key, stale, and unknown-subscription events. State which cases remain quarantined. Keep tenant labels beside every expected state.
Run isolation fixtures
Process events for both tenants through the real receiver. Confirm each record stays scoped, similar keys do not collide, and ambiguous identity cannot use a global or current-user fallback. Compare both tenant identifiers.
Check retry and recovery
Repeat an ambiguous event after mapping correction and process a duplicate. Verify tenant context, deduplication, state, and effect remain correct. Keep event and subscription IDs in safe correlation output. Keep subscription and endpoint identifiers in the result.
What to carry forward
Accept when valid events reach only their tenant, ambiguous identity stops safely, similar keys remain isolated, and recovery preserves scope. Keep external subscription mapping partial when uncontrolled. Record fixtures, authorization context, and results. Keep a global fallback out of the receiver path.
Technical background: GitHub 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