Quotas and Limits | MuleSoft Documentation
# Quotas and Limits
The following table shows the quotas and limitations of the IDP service:
Limit | Description  
---|---  
Accepted File Formats |  PDF, PNG, JPG, TIFF (150 DPI or more recommended) The document action builder does not support previewing TIFF files. However, you can extract data and review results from these files.  
File Size Limits |  | Upload via UI | Upload via API  
---|---  
  * 10 files per upload
  * 50 pages per file
  * 8 MB per file

| 
  * 1 file per API request
  * 50 pages per file
  * 10 MB per file

  
Prompt Limits | 
  * 30 per document action If **Customize Schema** is disabled.
  * English prompts Prompts in other languages are not fully supported.
  * Unique prompts Duplicate prompt names or instructions are not allowed. The Generic document action supports duplicate instructions if **Customize Schema** is enabled.
  * 128,000 tokens per request for Einstein prompts
    * 30,000 tokens per request for Einstein prompts when PII masking is enabled
The total number of tokens in a request includes:
    * The text contained in the source document to analyze
    * The image to analyze with image recognition capabilities
    * The sum of all field, table, column names with their corresponding intructions and the schema built through **Customize Schema**
    * Approximately 1,000 tokens that IDP uses to process the request

  
Prompt Response Limits | 
  * 128 characters for IDP NLP prompts
  * Approximately 3,000 output words for Einstein prompts using `GPT-4o (gpt-4o-2024-05-13)`
  * Approximately 4,000 output words for Einstein prompts using `GPT-4o (gpt-4o-2024-08-06)` or `GPT-4o Mini (gpt-4o-mini-2024-07-18)`
  * Approximately 6,000 output words for Einstein prompts using `Einstein GEMINI-2.0 Flash 001`

  
Request Limits | 
  * IDP fails the execution when the number of requests exceeds the Einstein rate limit for the Salesforce Org
    * When using Einstein and **Customize Schema** is enabled: 300 requests per minute
    * When using Einstein and **Customize Schema** is disabled: (300 / number Einstein of prompts in document action) requests per minute
  * 100 concurrent jobs per minute

  
Document Languages |  Language support varies depending on the selected large language model (LLM) in document actions. For a list of supported languages by provider, see:
  * OpenAI’s supported languages
  * Gemini’s supported languages

  
Polling Limits |  10-second interval for retrieving results Applications must avoid polling for results more often than every 10 seconds.  
Checkboxes | Accuracy of checkbox processing varies by model depending on form complexity. Test thoroughly on many representative documents to confirm acceptable performance for your use case. See Supported Models for more information about how each model performs when processing checkboxes.  
## Token Usage and Estimation
A token is a unit of text that a large language model (LLM) processes. Tokens are essential for breaking down input data into manageable pieces that can be analyzed and generated. These are some estimated conversions that might help understand token lengths:
  * 1 token ~= 4 characters
  * 1 token ~= ¾ words
  * 1-2 sentences ~= 30 tokens
  * 1,500 words ~= 2048 tokens


When analyzing images, each model uses a different tokenization strategy that affects how they calculate tokens. Refer to each provider’s documentation for additional guidance:
  * Gemini: token usage estimation for images
  * OpenAI: token usage estimation for images


## Document Retention Policy
IDP retains the document files and extracts data as needed to process the document extractions. IDP uses the following features to enhance data retention:
  * Document Action Editor
IDP temporarily stores the files you modify in the editor during the testing process and immediately removes these files after you close the editor. IDP also removes the extracted data and the files when you end the session or upload a new file.
  * Document Action Execution Endpoint
When you use the execution endpoint API, IDP stores the files in an S3 bucket and stores the data extracted during the execution securely.


For all successful executions, IDP retains this data for 24 hours. For executions that require human review, IDP retains this data for seven days after the user task is completed. IDP retains any incomplete tasks for 30 days. Currently, you cannot configure these retention periods.
## Data Residency Policy:
IDP uses AWS services such as S3 and RDS to store files and the extracted data. IDP currently supports 2 regions: US (Virginia) and EU (Frankfurt, Germany). IDP stores the data closest to your Anypoint control plane region to ensure GDPR requirements. For example, if your Anypoint control plane runs in the EU region, IDP stores your data in the Frankfurt data center.
## See Also
  * Automation Credits Usage and Rates
  *