Build a useful investigation brief
Map each transition
Write the route, form submission, response, and resulting page for workspace creation, project creation, test-key creation, and the check. Note where Turbo or a redirect changes context. Preserve status and validation messages while excluding secrets from the investigation brief.
Compare durable state
After each step, inspect only authorized synthetic records to confirm whether the project, key metadata, and check result were saved. A blank guide can reflect a stale read, a failed write, or a permission filter. Treat each as a possibility until the record and response agree.
Check role and recovery
Repeat the path as the workspace owner and a non-owner where those roles are supported. Test refresh, back navigation, and a return to the workspace after an interrupted submission. Record whether the next action remains scoped to the same workspace and project.
What to carry forward
The investigation is ready when the setup sequence shows the first divergence between visible state and durable state, including route, role, response, and record evidence. Deliver open hypotheses and recovery limits; do not call a person’s pause a technical cause without supporting evidence.
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