The queue lets clients line up more requests than their plan allows at once. Requests over the limit wait in a Queued status, and the client decides which ones come next by reordering the queue.
Use case: your Design Subscription includes 3 active requests at a time. A client submits a fourth and a fifth. Instead of you juggling priorities over email, the extra requests wait in their queue, and the client drags the most urgent one to the top.
How the queue works
The limit comes from the service, not the subscription: it's the Max concurrent Requests field on the service's pricing details. Leave it empty and there is no limit (and no queue).
The limit counts open requests per organization and per service. If an organization has two services with a limit, each service has its own queue.
When a new request is created for a client and their organization already has that many open requests on the service, the new request gets the Queued status instead of your Status after creation.
On recurring services, when an active request is completed, the first queued request moves up automatically and gets your Status after creation.
Queued requests don't count as active requests and don't show as a column in Kanban view.
How to turn on the queue
Go to Settings > Modules and extensions and open Requests.
Turn on Requests queue.
Under Queued status, pick the status used for queued requests (for example, Queued). It must be different from your completed, closed and after-creation statuses.
Click Save.
How to set the limit on a service
Go to Services > All services and open the service.
Click Edit service, then Next to reach Pricing details.
Under Max concurrent Requests, enter how many requests can be active at once.
Finish the steps and save the service.
Read more in How to manage the max number of active requests.
How your clients use the queue
When the queue is on and a client has a service with a limit, their Requests page opens in Queue view. They can switch views at any time from the view menu at the top right.
Queue view has two sections:
Active: requests your team is working on, numbered in priority order.
Queued: requests waiting for a free slot.
To reorder, your client can:
Drag a request up or down by its handle to change its priority.
Drag a request between Active and Queued. If moving it into Active goes over the service's limit, a message warns that the queue will be reordered to fit the limit.
Or click the three dots on a request and choose Move to queue or Move to Active.
On a request's page, clients who reached their limit see a banner saying that any new requests will be added to their queue.
How to see a client's queue
You don't need to impersonate the client. Go to Users > Clients, open the Organizations tab, click the organization and select the Requests tab. Choose Queue in the view menu to see the same Active and Queued lists your client sees, and reorder them if needed.
To find queued requests across all clients, go to Requests, open Filters and choose the Queued status.
FAQ
Why don't I see the Queue option?
The Queue view only appears when Requests queue is on and the organization has at least one open or queued request on a service with Max concurrent Requests set. Without a limit, there's nothing to queue.
What happens when a subscription is paused?
Pausing doesn't send requests to the queue. While a subscription is paused, the client can't submit new requests on that service, unless you ticked Accept new requests when you paused it. See How to disable the cancel or pause subscription option.
What if my team changes a queued request's status by hand?
Whenever a request enters or leaves the Queued status, or is completed, ManyRequests recalculates the queue so the service's limit is respected. If the service is already at its limit, a request may go back to the queue. To change the order, reorder the queue instead.