AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
backendcritical PriorityID: fastapi-lifespan-taskgroup-cancellation-standard

FastAPI Lifespan Structured Concurrency & TaskGroup Graceful Cancellation

Enforces deterministic structured concurrency within FastAPI lifespan contexts using Python 3.11+ TaskGroups or AnyIO task groups. Prevents unhandled dangling coroutines, post-teardown execution against closed connection pools, and unorderly process termination across multi-worker ASGI environments during SIGTERM/SIGINT events.

Prohibited Anti-Pattern: Unscoped fire-and-forget asyncio.create_task calls causing worker shutdown corruption and orphaned coroutines

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: FastAPI Lifespan Structured Concurrency & TaskGroup Graceful Cancellation - Enforces deterministic structured concurrency within FastAPI lifespan contexts using Python 3.11+ TaskGroups or AnyIO task groups. Prevents unhandled dangling coroutines, post-teardown execution against closed connection pools, and unorderly process termination across multi-worker ASGI environments during SIGTERM/SIGINT events.
globs: app/**/*.py, src/**/*.py, **/main.py, **/lifespan.py, **/dependencies.py
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/fastapi-lifespan-taskgroup-cancellation-standard"
---

# FastAPI Lifespan Structured Concurrency & TaskGroup Graceful Cancellation

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: Unscoped fire-and-forget asyncio.create_task calls causing worker shutdown corruption and orphaned coroutines

## System Constraints
You are a Principal Software Architect enforcing deterministic structured concurrency in FastAPI. Reject any fire-and-forget background tasks initiated via raw `asyncio.create_task` or FastAPI `BackgroundTasks` for long-running processes. Mandate that all asynchronous workers, message consumers, and persistent loops are anchored to a bounded `asyncio.TaskGroup` or AnyIO task group managed strictly within the lifespan context manager, ensuring task cancellation and completion prior to database and connection pool teardown.

## Strict Guidelines
- Engineers MUST ALWAYS manage background workers and long-lived coroutines within an explicit structured concurrency boundary (Python 3.11+ `asyncio.TaskGroup` or Starlette-native `anyio.create_task_group`) attached to the application lifespan context.
- Engineers MUST NOT instantiate unmanaged tasks via `asyncio.create_task()` without retaining references and explicitly orchestrating their cancellation prior to dependency teardown.
- Code MUST drain and cancel all background tasks BEFORE closing upstream connection pools (PostgreSQL, Redis, RabbitMQ, Kafka) to prevent coroutines from failing against closed client sessions.
- Lifespan handlers MUST wrap task cancellation in explicit timeouts (e.g., `asyncio.timeout(10.0)`) to guard against deadlocked coroutines hanging the worker shutdown sequence.
- Services MUST catch and gracefully swallow `asyncio.CancelledError` inside long-running coroutines, ensuring state cleanup routines execute before the coroutine returns.
- Components NEVER rely on FastAPI `BackgroundTasks` for persistent loops or critical mutations that outlive the HTTP response lifecycle in distributed ASGI deployments.

## Bad vs Good Implementations
### Lifespan Structured Concurrency via TaskGroup and Controlled Draining

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Raw `asyncio.create_task` creates an orphaned coroutine that is not tracked by the lifespan manager. When Uvicorn receives SIGTERM, the yield block resumes, immediately closing `db_pool`. The ongoing background task subsequently crashes with connection pool closed errors, leaking uncommitted transactions or corrupting state.
```python
import asyncio
from contextlib import asynccontextmanager
from fastapi import FastAPI

async def background_metric_sync():
    while True:
        await asyncio.sleep(5)
        # Violates lifespan boundaries: executes against closed DB when server halts
        await sync_metrics_to_db()

@asynccontextmanager
async def lifespan(app: FastAPI):
    # ANTI-PATTERN: Unscoped fire-and-forget task without lifecycle binding
    asyncio.create_task(background_metric_sync())
    yield
    # Database pool is closed while background_metric_sync is still running!
    await app.state.db_pool.close()
```

#### Production Standard (Correct)
> **Standard**: Using `asyncio.TaskGroup` ensures that all background tasks remain bounded within the lifespan context. Upon shutdown, tasks are explicitly cancelled and awaited before execution leaves the `TaskGroup` context manager. Connection pools are dismantled only after background workers have completely drained and terminated.
```python
import asyncio
from contextlib import asynccontextmanager
from fastapi import FastAPI

async def background_metric_sync():
    try:
        while True:
            await asyncio.sleep(5)
            await sync_metrics_to_db()
    except asyncio.CancelledError:
        # Orderly exit upon cancellation request
        await finalize_metric_buffer()
        raise

@asynccontextmanager
async def lifespan(app: FastAPI):
    # Initialize infrastructure connection pools first
    app.state.db_pool = await create_db_pool()
    
    # Enforce structured concurrency boundary for background tasks
    try:
        async with asyncio.TaskGroup() as tg:
            app.state.bg_task_group = tg
            worker_task = tg.create_task(background_metric_sync())
            
            # Application accepts traffic
            yield
            
            # Trigger cooperative cancellation during shutdown
            worker_task.cancel()
    except* asyncio.CancelledError:
        # Clean TaskGroup unwind following task cancellation
        pass
    finally:
        # Guaranteed to execute only after all TaskGroup tasks have exited
        async with asyncio.timeout(5.0):
            await app.state.db_pool.close()
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

FastAPI Lifespan Concurrency Validator
AST inspector to verify ASGI lifespan compliance and structured concurrency patterns in Python backends.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Ruff AsyncIO Static Analysis Audit
Lints for unassigned asyncio.create_task calls (RUR001) and ensures strict structured concurrency across ASGI projects.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: FastAPI Lifespan Structured Concurrency & TaskGroup Graceful Cancellation

FastAPI Lifespan Structured Concurrency & TaskGroup Graceful Cancellation defines an industrial-grade behavioral standard for backend engineering. Enforces deterministic structured concurrency within FastAPI lifespan contexts using Python 3.11+ TaskGroups or AnyIO task groups. Prevents unhandled dangling coroutines, post-teardown execution against closed connection pools, and unorderly process termination across multi-worker ASGI environments during SIGTERM/SIGINT events. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Unscoped fire-and-forget asyncio.create_task calls causing worker shutdown corruption and orphaned coroutines Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftUnscoped fire-and-forget asyncio.create_task calls causing worker shutdown corruption and orphaned coroutinesCritical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS manage background workers and long-lived coroutines within an explicit structured concurrency boundary (Python 3.11+ `asyncio.TaskGroup` or Starlette-native `anyio.create_task_group`) attached to the application lifespan context.

Engineers MUST ALWAYS manage background workers and long-lived coroutines within an explicit structured concurrency boundary (Python 3.11+ `asyncio.TaskGroup` or Starlette-native `anyio.create_task_group`) attached to the application lifespan context.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT instantiate unmanaged tasks via `asyncio.create_task()` without retaining references and explicitly orchestrating their cancellation prior to dependency teardown.

Engineers MUST NOT instantiate unmanaged tasks via `asyncio.create_task()` without retaining references and explicitly orchestrating their cancellation prior to dependency teardown.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Code MUST drain and cancel all background tasks BEFORE closing upstream connection pools (PostgreSQL, Redis, RabbitMQ, Kafka) to prevent coroutines from failing against closed client sessions.

Code MUST drain and cancel all background tasks BEFORE closing upstream connection pools (PostgreSQL, Redis, RabbitMQ, Kafka) to prevent coroutines from failing against closed client sessions.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Lifespan handlers MUST wrap task cancellation in explicit timeouts (e.g., `asyncio.timeout(10.0)`) to guard against deadlocked coroutines hanging the worker shutdown sequence.

Lifespan handlers MUST wrap task cancellation in explicit timeouts (e.g., `asyncio.timeout(10.0)`) to guard against deadlocked coroutines hanging the worker shutdown sequence.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Services MUST catch and gracefully swallow `asyncio.CancelledError` inside long-running coroutines, ensuring state cleanup routines execute before the coroutine returns.

Services MUST catch and gracefully swallow `asyncio.CancelledError` inside long-running coroutines, ensuring state cleanup routines execute before the coroutine returns.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
6

Components NEVER rely on FastAPI `BackgroundTasks` for persistent loops or critical mutations that outlive the HTTP response lifecycle in distributed ASGI deployments.

Components NEVER rely on FastAPI `BackgroundTasks` for persistent loops or critical mutations that outlive the HTTP response lifecycle in distributed ASGI deployments.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is FastAPI Lifespan Structured Concurrency & TaskGroup Graceful Cancellation critical for AI coding assistants?

Enforces deterministic structured concurrency within FastAPI lifespan contexts using Python 3.11+ TaskGroups or AnyIO task groups. Prevents unhandled dangling coroutines, post-teardown execution against closed connection pools, and unorderly process termination across multi-worker ASGI environments during SIGTERM/SIGINT events. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Unscoped fire-and-forget asyncio.create_task calls causing worker shutdown corruption and orphaned coroutines) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related BACKEND Rules

View all rules →
backend
42

Fastify 5 Schema Compilers & Encapsulation Production Standard

Fastify relies on lexical encapsulation contexts to sandbox decorators, hooks, and compiled validation/serialization schemas without memory leaks or cross-tenant bleed. In Fastify 5, misuse of global compilers or failing to encapsulate plugin boundaries causes compiled `fast-json-stringify` serializers and Ajv validators to either crash on duplicate IDs, leak private data across sibling scopes, or bypass JIT compilation optimizations. Production services must enforce strict encapsulation hierarchies and type-safe schema compilation across every routing subtree.

backend
68

Bun Embedded SQLite WAL Mode & Transaction Synchronization Standard

Production database standard for bun:sqlite. Mandates enabling Write-Ahead Logging (PRAGMA journal_mode = WAL), busy timeouts, and using db.transaction() for atomic operations without lock starvation.

backend
68

Drizzle ORM Batch API & Interactive Transaction Isolation Standard

Production database standard for Drizzle ORM (PostgreSQL & MySQL). Mandates using db.batch() over HTTP drivers to prevent round-trip waterfalls, explicit db.transaction() with serializable/read-committed isolation, and strictly avoids unawaited query promises.

1 Rule in Stack

FastAPI