Build a useful investigation brief
Trace key and context
Map the project route, test-key metadata, intake action, request status, and resulting redirect. Verify the key belongs to the selected synthetic project without exposing its secret. Compare a fresh key with an invalid, missing, or wrong-project fixture where supported.
Follow processing state
Record queued, processing, saved, failed, and unknown states for one built-in sample attempt. Refresh the overview and follow links as each state changes. Treat a delayed local transition as a timing observation until the durable sample record and status can be compared.
Compare generated evidence
Inspect the saved sample Signal and linked Work Item for labels, project scope, identifiers, and status. Check whether the setup result appears in the same workspace and project as the initiating owner. Keep any producer or external event expectation outside this local investigation.
What to carry forward
The investigation is ready when key context, request status, processing state, and generated records can be followed for one synthetic check. Deliver the first divergence and the timing or processing boundary that remains unknown, with no claim that the local sample represents another system.
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