# How processing works

## How processing works
- A background task runs **every 5 seconds** and atomically claims up to **10 entries** from each queue.
- Each entry calls the same logic as the single-user endpoint (`pauseEnrollment()`, `resumeEnrollment()`, `closeUserAccount()`), so behavior matches what you'd get from a one-off API call.
- On failure, errors are recorded on the queue entry and visible in the portal.

Version: v3

## Description:

  - `How processing works` ()
    A background task runs every 5 seconds and atomically claims up to 10 entries from each queue.Each entry calls the same logic as the single-user endpoint (pauseEnrollment(), resumeEnrollment(), closeUserAccount()), so behavior matches what you'd get from a one-off API call.On failure, errors are recorded on the queue entry and visible in the portal.