---
title: "Comment by Mm Cc on \"Rules of Structured Concurrency\" | Hashnode"
description: "Great breakdown of structured vs. unstructured tasks. One complementary tip: when using TaskGroup , explicitly handle child task errors within the group block t"
url: "https://hashnode.com/posts/rules-of-structured-concurrency/67f2bb1049ea7db6aa9cbd00/comment/69d795c2c2e492803f380a6a"
---

[Discussion](https://hashnode.com/posts/rules-of-structured-concurrency/67f2bb1049ea7db6aa9cbd00)

Comment [Rules of Structured Concurrency](https://hashnode.com/posts/rules-of-structured-concurrency/67f2bb1049ea7db6aa9cbd00)

[Mm Cc](https://hashnode.com/@mmcc)

[Apr 9](https://hashnode.com/posts/rules-of-structured-concurrency/67f2bb1049ea7db6aa9cbd00/comment/69d795c2c2e492803f380a6a)

Great breakdown of structured vs. unstructured tasks. One complementary tip: when using `TaskGroup`, explicitly handle child task errors within the `group` block to prevent a thrown error from automatically canceling all other child tasks—this gives you finer control over failure scenarios.
