# Background jobs that hang or stop halfway

Prompt · Infrastructure and environment · I04

Finds scheduled jobs and background workers that can hang, overlap or stop halfway.

## Prompt

```text
Find background jobs that can block other work or leave partially updated data. Examine queues, locks, timeouts, retries, deployment behavior, and observability.
```

**What it returns:** Each job with its trigger, timeout, what happens if two run at once, and what happens if it dies midway.

**Skip it when:** Projects with no background jobs.

**Tools:** Repository, the scheduled jobs in vercel.json, logs.

**Changes:** Changes nothing

**Sessions:** One session

## Related

- [Half-finished failures](https://www.atlasscope.dev/prompts/half-finished-failures): Finds what is left behind when something fails halfway.
- [Safe to run twice?](https://www.atlasscope.dev/prompts/safe-to-run-twice): Finds actions that do damage when they run twice: double sends, double charges, duplicate rows.
- [Database changes during a deploy](https://www.atlasscope.dev/prompts/database-changes-during-a-deploy): Checks that each database change works with the old code that is still live while a release finishes.

Source: https://www.atlasscope.dev/prompts/background-jobs-that-hang-or-stop-halfway