Use case: Your plans promise a set amount of work, for example "2 active requests at a time" or "10 requests a month". You can set both limits on each service, and ManyRequests tells you and your client when a limit is reached.
Set the limits on a service
Go to Services > All services.
Click the service's name, or click the three dots on its row and choose Edit.
Review the service details and click Next to open Pricing details.
Scroll to More details and fill in the limits:
Max concurrent requests: how many of the client's requests on this service can be open at the same time. Leave it empty for no limit.
Max number of requests per month: how many requests the client can create on this service each month. Recurring services only. Leave it empty for no limit.
Click Next, adjust the request form if needed, and save the service.
One-off services have Max concurrent requests too, in the same More details section. When you create a new service, you set these limits in the same place.
What counts as an open request
Only requests in an open status count toward Max concurrent requests. Completed, closed and queued requests don't. The limit applies per client organization and per service.
What happens when a limit is reached
On the request page, your team sees a banner such as "The client has reached the maximum number of concurrent requests allowed for their plan."
Your client sees "You have reached the maximum number of active requests allowed for your plan. Please note any new requests will be added to your queue." When the monthly limit is reached, the message says so instead.
What happens to new requests depends on the Requests queue setting:
Queue on: new requests above the limit get the Queued status. On recurring services, the first queued request moves up automatically when an open request is completed. Clients can reorder their queue.
Queue off: the limit is shown in the banners, but new requests are not held back.
To change it, go to Settings > Modules and extensions > Requests and turn Requests queue on or off. See How to use the requests queue for the full queue workflow.
