Decide where the work belongs
Rank blocked and early paths
For each occurrence, record dependents waiting, downstream action, and whether a prerequisite was missing, failed, or simply slow. Put an early release and its possible side effect ahead of a bounded wait. Include the graph depth affected by the state.
Compare prerequisite outcomes
Group waits by all-success, one failure, cancellation, missing prerequisite, and delayed terminal event. Note which edges and fan-in rules are confirmed. A stale projection affecting one edge needs a different queue decision from a scheduler that never creates the prerequisite.
Choose a graph-safe next step
Select immediate reconciliation, an edge or fan-in review, or one controlled prerequisite trace. State what must be read before releasing or replaying a dependent. Avoid manually marking a dependent ready while its prerequisite state remains unknown.
What to carry forward
Queue the issue with graph reach, blocked or early consequence, prerequisite evidence, and release safety. Escalate when dependents can run before required inputs or remain ownerless. Otherwise schedule a focused edge investigation with success, failure, and missing-prerequisite controls.
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