# Timers and connections nobody closes

Prompt · Architecture and hidden complexity · A07

Finds timers, listeners and connections that nobody clearly owns or shuts off.

## Prompt

```text
Map external side effects and resource lifecycles across this application: connections, subscriptions, listeners, timers, streams, cache entries and background workers. Find unclear ownership, incomplete cleanup and operations that outlive their intended scope. Prioritize evidenced leaks or correctness risks over stylistic patterns.
```

**What it returns:** Each resource with where it is created, who should release it, and the path where it is not released.

**Skip it when:** Short-lived scripts and one-off server functions that keep nothing running between calls.

**Tools:** Repository access; memory snapshots help confirm.

**Changes:** Changes nothing

**Sessions:** One session

## Related

- [Memory that keeps growing](https://www.atlasscope.dev/prompts/memory-that-keeps-growing): Finds why a page or process gets slower or crashes the longer it runs.
- [Half-finished failures](https://www.atlasscope.dev/prompts/half-finished-failures): Finds what is left behind when something fails halfway.

Source: https://www.atlasscope.dev/prompts/timers-and-connections-nobody-closes