When you act on many users at once — pause, resume, or close — CRS handles the work asynchronously through two background queues. You submit the batch, get an immediate response, and we process the users one by one in the background. Async processing is necessary because each operation hits Equifax — pausing or closing a user requires us to update their enrollment with the bureau, which takes a noticeable round-trip per user. Doing 10,000 of those serially in a synchronous request would time out long before completion; queueing the work lets us pace the calls, retry transient failures, and stay within Equifax's rate limits without forcing your batch endpoint to hold a connection open.
The two queues — Enrollment (pause/resume) and Unenrollment (close) — are independent: an item moves through its queue with retries on transient errors and a terminal failure state if Equifax permanently rejects the change. Below you'll find how to inspect queue state, how retries and terminal failures behave, and where in the Customer Portal to monitor live processing.
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.