Build a useful investigation brief
Prepare prerequisite outcome cases
Create sanitized graphs with all prerequisites succeeding, one failing, one canceled, one missing, and one delayed. Record the expected dependent state for each. Keep IDs and graph revision fixed so outcome mapping is the variable under test.
Trace fan-in and release
Capture prerequisite terminal events, dependency state projection, edge evaluation, release reason, dependent ready or wait record, and claim. Check whether one success can satisfy a rule that requires all prerequisites and whether stale state persists after a late event.
Test one edge mapping
Exercise one explicit edge or fan-in correction against the outcome matrix and compare dependent readiness and terminal states. Keep timeout behavior separate if it uses a different contract. Preserve a missing-prerequisite result rather than treating absence as success.
What to carry forward
Deliver the graph outcome matrix, edge and fan-in trace, first release divergence, and one tested mapping. State whether the next work belongs to prerequisite creation, state projection, release logic, timeout, or dependent handling. Keep delayed events and missing IDs explicit.
Technical background: Celery 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