Knowledge Center

Knowledge Center > RBM Solutions > Policies > Concurrent Request Limits

Concurrent Request Limits

Zuora enforces tenant-level concurrent request limits from the user interface and Zuora REST and SOAP API. This policy prevents tenants from monopolizing Zuora system resources.

Concurrent Request Limits

Each Zuora tenant has the following default concurrent request limits:

Type Description Default Limit for Concurrent, Uncompleted Requests Retry After
Total Request Refers to UI, REST, and SOAP API requests processed under a tenant.
  • API calls (REST and SOAP)
    • Create
    • Update
    • Delete 
    • Generate
    • Query
  • UI requests (all - including Big Data Requests, and Big Process Requests)
  • Zuora for Salesforce
    • Zuora 360 Order Builder (includes APEX wrappers for SOAP APIs)

Excluded from this policy

  • Login API calls (REST and SOAP) 
  • UI login requests
  • Zuora for Salesforce
    • 360 Sync
    • Zuora Quotes
  • Custom requests
200 120 seconds
Big Process Request

Refers to database operation-heavy requests. The following lists the SOAP API calls that are handled as Big Process Requests and the objects they support.

create()

invoice

generate()

invoice

queryMore()

Account

InvoiceItem

PaymentTransactionLog

RatePlan

RatePlanCharge

RatePlanChargeTier

Subscription

query()

Account

Invoice

InvoicePayment

Payment

PaymentTransactionLog

RatePlan

RatePlanCharge

Subscription

Usage

20
Big Data Request Data transfers to or from Zuora, such as a usage upload or data source file download. 20

Custom

Includes all of the following:

Subscribe and amend REST method calls:

Subscribe and amend SOAP calls:

  • Amend
  • Subscribe
  • Subscribe with existing account

Hosted Payment Method Pages:

Custom requests are not counted against the total number of requests allowed at any given time. 

40

 

FAQs

How do I know if I have reached a limit?

You will encounter the following error codes, error messages, or HTTP status codes:

Request Type Error Code Error Message HTTP Status Code - Response Header
User Interface N/A "The total number of concurrent requests has exceeded the limit allowed by the system. Please resubmit your request later."

N/A

REST API 50000070 "The total number of concurrent requests has exceeded the limit allowed by the system. Please resubmit your request later."

HTTP Status: 429

Response Header:   “Retry-After:120"

SOAP API, version 51.0 and later

<fns:FaultCode>
REQUEST_EXCEEDED_LIMIT
</
fns:FaultCode>

<fns:FaultMessage>
The total number of concurrent requests has exceeded the limit allowed by the system. Please resubmit your request later.
</fns:FaultMessage>

HTTP Status: 429

Response Header:   “Retry-After:120"

SOAP API, versions prior to 51.0

<fns:FaultCode>
UNKNOWN_ERROR </fns:FaultCode>

<fns:FaultMessage>
The total number of concurrent requests has exceeded the limit allowed by the system. Please resubmit your request later.
</fns:FaultMessage>

HTTP Status: 429

Response Header:   “Retry-After:120"

File Download API N/A "The total number of concurrent requests has exceeded the limit allowed by the system. Please resubmit your request later."

HTTP Status: 429

Response Header:   “Retry-After:120"

After I have reached the limit, when can I retry sending a request?

Zuora recommends waiting 120 seconds and then retry sending the request.

Can the default threshold settings affect my subscribe or amend calls?

No.

How do I design integrations to avoid these limits?

We recommend using the apisandbox to test your integrations. Contact support@zuora.com if you require additional assistance. 

How is Zuora for Salesforce impacted by this policy?
The following Zuora for Salesforce products are excluded from the Concurrent Request Limit Policy:
  • Zuora Quotes
  • 360 Sync

The following Zuora for Salesforce are included in this policy:

  • Zuora 360 Order Builder incuding APEX wrappers for Zuora SOAP call.
  • Hosted Payment Method Pages (PublicHostedPaymentMethodPage.do and PublicHostedPage.do URLs)
Last modified
12:32, 22 Apr 2015

Tags

Classifications

(not set)