Block tasks from closing until subtasks and dependencies are done

The system stops a task from being marked done until its subtasks and dependencies are finished.

How the work actually flows

It branches. Exactly one path is taken; runs once per one per subtask or dependency.

Pattern: Exclusive Choice (4) · Multiple Instances with a priori Design-Time Knowledge (13)

flowchart TD trig>"task marked as done"]:::trig s0[["check subtasks and dependencies"]]:::mi s1["determine if items still open"]:::task trig --> s0 s0 --> s1 gx{"× any subtask still open"}:::gate s1 --> gx p00["roll back status"]:::task gx -->|"items open"| p00 p01["notify person why"]:::task p00 --> p01 p10["task stays closed"]:::task gx -->|"all items done"| p10 p01 --> out p10 --> out out[/"task closes only when complete"/]:::out pay{{"prevents premature task closure"}}:::pay out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepRuns once per itemOne path onlyResultPayoff
Build size
Advanced

A larger build with multiple systems, AI reasoning, and custom rules.

Business functions
API & Webhook Integration
Connects
Awork

The problem it solves

You mark a project task as done, only to find out later that a subtask or a dependent piece of work was never finished. Catching these gaps manually means someone has to remember to check every related task before closing anything out. Small oversights like this can quietly derail a project timeline.

Who it fits

A project or operations team managing tasks with subtasks and dependencies.

How it works

  1. A task's status changes to done
  2. The system checks all of its subtasks and dependent tasks
  3. If any of them are still open, the task status is rolled back
  4. The person who tried to close it is notified why
What you get

Tasks that never close before they're ready

A task can't be marked done until every subtask and dependency underneath it is actually finished, keeping your project status honest.

What you get

A task list that only shows work as done when everything underneath it is actually finished.

What you need

An Awork account with API access.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook