Establish what is happening
Freeze environment evidence
Record endpoint origin, configured environment, receiver revision, safe event and resource identifiers, credential or secret label, and downstream disposition. Do not copy secret values. Note whether the event was synthetic, live, or unknown from a trusted source.
Compare route and resource
Match environment configuration, endpoint, verification context, event metadata, tenant or resource marker, and resulting workflow. Distinguish an event accepted by the wrong receiver from one rejected before any effect. Preserve both expected and observed environments.
Bound possible exposure
Group reports by endpoint, environment, receiver revision, event source, resource type, and effect. Separate one misrouted fixture from a copied shared secret or missing environment marker. Keep unknown events quarantined for review rather than guessing live status.
What to carry forward
Triage is complete when one mixed-environment delivery has a reproducible trigger, first routing boundary, affected scope, and explicit unknowns. Hold broad replay or credential changes. Route endpoint, configuration, marker, and resource questions separately with a clear owner.
Technical background: OpenAI 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