# Why queues exist

## Why queues exist
Pausing, resuming, or closing thousands of users in a single API call would tie up your request for minutes and risk timeouts. Instead, batch endpoints **accept the list immediately** and queue the work. Each user is then processed by a background worker that runs every few seconds — calling the underlying single-user operation, tracking the result, and retrying transient failures.
You can monitor the state of every queued user in the [Customer Portal](/client-spec/customer-portal) at any time.

Version: v3

## Description:

  - `Why queues exist` ()
    Pausing, resuming, or closing thousands of users in a single API call would tie up your request for minutes and risk timeouts. Instead, batch endpoints accept the list immediately and queue the work. Each user is then processed by a background worker that runs every few seconds — calling the underlying single-user operation, tracking the result, and retrying transient failures. You can monitor the state of every queued user in the Customer Portal at any time.