Parent Tasks and Sub-Tasks No Longer Run at the Same Time

Summary

When a task is broken down into sub-tasks, Effigate Command Center now enforces a strict, predictable order for how the parent task and each sub-task run — the parent plans, each stage of sub-tasks runs in turn, and the parent wraps everything up at the end. Several long-standing reliability problems with staged work all traced back to the same gap: nothing previously stopped a parent task's own agent from running at the same time as the sub-tasks it was meant to be coordinating.

What You Gain

Previously, a parent task's coordinating agent could end up redoing the very work its sub-tasks were created to handle, because the instructions it worked from didn't always reflect the breakdown that had just been created. Separately, assigning every sub-task at once could start the parent and its first stage of sub-tasks together instead of in sequence, and an urgent parent task's own queued work could jump ahead of the sub-tasks it was actually waiting on. On top of that, moving an agent-assigned task back into an active column from certain views sometimes did nothing at all — the task just sat there.

All of this is now fixed by enforcing one clear lifecycle: the parent plans the breakdown, the first stage of sub-tasks runs, the parent checks in on what came back and can still adjust later stages, the next stage runs, and so on — until every sub-task is finished, at which point the parent does its final integration and wraps up the whole piece of work. Each step only begins once the previous one has actually finished, so nothing has to remember to hand off to the next step, and a stage that fails or needs your attention still moves the whole chain forward rather than leaving it stuck.

How It Works

• A sub-task created while its parent is actively working is automatically held back, with a clear explanation of why and what happens next.
• Sub-tasks inherit their parent's priority, so an urgent parent's work is no longer queued behind sub-tasks whose own priority was lower by default.
• Moving an agent-assigned task into an active column reliably starts the agent now, whichever view you move it from.
• When a task's run is intentionally held back because its sub-tasks are still working, that shows up directly on the task's own activity timeline, so "why hasn't this started" always has an answer.
• The whole lifecycle — plan, run each stage, check in, integrate — is enforced consistently, so a parent task can no longer duplicate or race ahead of its own sub-tasks.

Where to Find It

This runs automatically for every project using staged sub-tasks — there's nothing to turn on, and it applies immediately to every account.

See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.