تاريخ آخر تحديث
13 سبتمبر 2024
Adobe Acrobat Sign transaction limits
Adobe Acrobat Sign limits transactions based on the service level of the sending party per the table below:
|
|
Transactions/ User License/ Year |
File size/ Upload |
Pages/ Transaction |
Signers/ Transaction |
KBA Transactions |
Phone Auth Transactions |
|---|---|---|---|---|---|---|
|
Acrobat Standard |
Unlimited (See below) |
10 MB |
100 |
10 |
0 |
0 |
|
Acrobat Pro |
Unlimited (See below) |
10 MB |
100 |
25 |
0 |
0 |
|
Acrobat Sign SMB |
150 (See below) |
10 MB |
100 |
25 |
0 |
0 |
|
Acrobat Sign for Business |
150 (See below) |
10 MB |
100 |
25 |
0 |
0 |
|
Acrobat Sign for Business |
150 (See below) |
10 MB |
100 |
25 |
50 |
50 |
|
Acrobat Sign for Enterprise |
150 (See below) |
10 MB |
500 |
25 |
50/yr |
50/yr |
|
Acrobat Sign for Enterprise |
150 (See below) |
10 MB |
500 |
25 |
50 |
50 |
Transactions/Acrobat Sign user: A transaction occurs each time an electronic document or collection of related electronic documents is sent to one or more End Users through Acrobat Sign.
Acrobat Sign plans sold as user licenses include 150 transactions per user per year unless otherwise stipulated in your contract.
Business and enterprise-level customers who process a high volume of transactions can speak to their sales agent about buying a total volume of transactions with unlimited users (or a site license).
Refer to the Transaction Consumption article for details on how transactions are consumed.
File size/Upload: Acrobat Sign limits the size of each file uploaded.
If you attempt to upload a document outside this boundary, you get an error under the file that says, "Upload limit exceeded."
Pages/Transaction: The whole transaction (all files merged together) has a total page limit.
If you attempt to send a document that is larger than your account set limit, you get the error "Acrobat Sign was unable to create your agreement because the document(s) exceeded your page limit."
Signers/Electronic transaction: The number of people who can sign an electronic signature transaction varies for each level of service.
Single-user, multi-user for teams, and business service levels have hard caps to the total number of signers their transactions can include.
KBA transactions: Knowledge-Based Authentication (KBA) is an advanced form of signer verification that is enabled at the business and enterprise level of service.
Phone Authentication transactions: Phone Authentication transactions are an advanced form of signer verification that is enabled at the business and enterprise levels of service.
Acrobat Sign monitors all client requests to protect system resources and ensure reliable service for all users. To prevent excessive resource consumption, requests from the same source—such as a user ID, IP address, or agreement ID—are limited per minute, hour, and day. If a request exceeds these limits, it is rejected with an error message.
In rare cases, if usage disrupts the system or affects Adobe’s ability to provide services, access to Acrobat Sign may be temporarily disabled. Below are the scenarios where Acrobat Sign enforces throttling.
Acrobat Sign processes all documents asynchronously, whether sent through the web interface or API when creating the following resources:
- Agreement
- Webform
- MegaSign
- Library Template
- Archive
To maintain reliable document processing and prevent slowdowns caused by large files, Acrobat Sign evaluates agreement limits based on the following:
- Total number of participants
- Total file size (including all uploaded files)
- Total number of pages processed
Limits apply on a per-user basis at the per-minute, per-hour, and per-day levels. All concurrent requests from a user—whether made through the web interface or API—are counted toward these limits.
If a request exceeds the allowed limits, an error message appears based on the specific use case when creating a resource through the Acrobat Sign user interface.
Webform
| You have reached the limit on the number of web forms you can create at this time. Please try again in {x} seconds/minutes/hours. |
Agreement
| You have reached the limit on the number of agreements you can send at this time. Please try again in {x} seconds/minutes/hours. |
Library Template
| You have reached the limit on the number of templates you can create at this time. Please try again in {x} seconds/minutes/hours. |
Archive
| You have reached the limit on the number of documents you can archive at this time. Please try again in {x} seconds/minutes/hours. |
Send in Bulk
When using Send in Bulk, a single API call or UI action creates multiple agreements and sends multiple signature requests. Because this process involves batch processing, Acrobat Sign does not enforce per-minute limits for Send in Bulk. However, per-hour and per-day limits still apply.
Before processing, Acrobat Sign evaluates the workload of the Bulk Send request.
- If the request stays within throttling limits, the system processes the Send in Bulk template and all associated child agreements.
- If the request exceeds the throttling threshold, it's declined before any child agreements are created. In this case, the user will see the following error message on the Send in Bulk compose page:
| You've reached the limit on the number of agreements you can send at this time. Please try again later. |
Webform Signing
Acrobat Sign creates a new agreement when a webform is signed, which then undergoes asynchronous document processing. This process is subject to the document processing throttling limits mentioned earlier.
Throttling limits apply to the user in the account that created the webform. If the agreement document processing exceeds these limits, the webform signer will see this error message:
This web form is very popular right now and can't be processed due to high demand. Please try again in {x} hours, {xx} minutes and {xxx} seconds. Contact the owner of this web form for further information. |
Contact your Customer Success Manager or Support to increase throttling limits. Provide the expected request volumes per minute, hour, and day, along with relevant details. Adobe will review your request and adjust the throttling limits to support your workflows at the required volume.
Webforms in Acrobat Sign have capabilities to have the Signer verify their email address. If this option is enabled, Acrobat Sign will limit how many times the first Signer/Participant can sign the webform (and/or add additional participants). Acrobat Sign has limits defined at each level - minute, hour, and day. Limits are enforced when the first signer/participant submits the webform. If the signer has exhausted the limits, the webform submission will be blocked and the participant see the below error message. The number of web forms submitted will be incremented after email verification by the first signer/participant is completed.
You've reached the limit on the number of times that you may access this web form. Please try again after {x} hours, {xx} minutes and {xxx} seconds. Contact the owner of this web form for further information. |
If the sending group has not enabled email verification for the first signer/participant, the agreements will not be throttled by the number of webform submissions.
You must contact your CSM or Support to increase threshold limits.
More about Acrobat Sign webforms can be found here: https://helpx.adobe.com/sign/adv-user/web-form/create.html
