---
schema_version: "1"
id: 5e090a2a954589eb0c48a62beea10afa6caafdbac7843e414401ff6a7c4bd444
title: Quotas and Limits
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/idp/quotas-and-limits.md
canonical_url: https://docs.mulesoft.com/idp/quotas-and-limits
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 7e717410e4f01c6ab5aa141bf7ef6d45f32cd8885bdb95e4e611718265b990f0
description: MuleSoft Documentation Site
latest: true
---
---
product: IDP
---

# Quotas and Limits

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

The following table shows the quotas and limitations of the IDP service:

<table><colgroup><col> <col></colgroup><thead><tr><th>Limit</th><th>Description</th></tr></thead><tbody><tr><td><p>Accepted File Formats</p></td><td><div><div><p>PDF, PNG, JPG, TIFF (150 DPI or more recommended)<br>The document action builder does not support previewing TIFF files. However, you can extract data and review results from these files.</p></div></div></td></tr><tr><td><p>File Size Limits</p></td><td><div><table><colgroup><col> <col></colgroup><thead><tr><th>Upload via UI</th><th>Upload via API</th></tr></thead><tbody><tr><td><div><div><ul><li><p>10 files per upload</p></li><li><p>50 pages per file</p></li><li><p>8 MB per file</p></li></ul></div></div></td><td><div><div><ul><li><p>1 file per API request</p></li><li><p>150 pages per file</p></li><li><p>15 MB per file</p></li></ul></div></div></td></tr></tbody></table></div></td></tr><tr><td><p>Prompt Limits</p></td><td><div><div><ul><li><p>30 per document action</p><div><p>If <strong>Customize Schema</strong> is disabled.</p></div></li><li><p>English prompts<br>Prompts in other languages are not fully supported.</p></li><li><p>Unique prompts</p><div><p>Duplicate prompt names or instructions are not allowed.</p></div><div><p>The Generic document action supports duplicate instructions if <strong>Customize Schema</strong> is enabled.</p></div></li><li><p>128,000 <a href="#tokens">tokens</a> per request for Einstein prompts</p><div><div><div><ul><li><p>30,000 tokens per request for Einstein prompts when PII masking is enabled</p></li></ul></div></div></div><div><p>The total number of tokens in a request includes:</p></div><div><ul><li><p>The text contained in the source document to analyze</p></li><li><p>The image to analyze with image recognition capabilities</p></li><li><p>The sum of all field, table, column names with their corresponding intructions and the schema built through <strong>Customize Schema</strong></p></li><li><p>Approximately 1,000 tokens that IDP uses to process the request</p></li></ul></div></li></ul></div></div></td></tr><tr><td><p>Prompt Response Limits</p></td><td><div><div><ul><li><p>128 characters for IDP NLP prompts</p></li><li><p>Approximately 3,000 output words for Einstein prompts using <code>GPT-4o (gpt-4o-2024-05-13)</code></p></li><li><p>Approximately 4,000 output words for Einstein prompts using <code>GPT-4o (gpt-4o)</code> or <code>GPT-4o Mini (gpt-4o-mini)</code></p></li><li><p>Approximately 48,000 output words for Einstein prompts using <code>Einstein GEMINI-3.5</code></p></li></ul></div></div></td></tr><tr><td><p>Request Limits</p></td><td><div><div><ul><li><p>IDP fails the execution when the number of requests exceeds the Einstein rate limit for the Salesforce Org</p><div><ul><li><p>When using Einstein and <strong>Customize Schema</strong> is enabled: 300 requests per minute</p></li><li><p>When using Einstein and <strong>Customize Schema</strong> is disabled: (300 / number Einstein of prompts in document action) requests per minute</p></li></ul></div></li></ul></div></div></td></tr><tr><td><p>Document Languages</p></td><td><div><div><p>Language support varies depending on the selected large language model (LLM) in document actions. For a list of supported languages by provider, see:</p></div><div><ul><li><p><a href="https://help.openai.com/en/articles/8357869-how-to-change-your-language-setting-in-chatgpt#h_513834920e">OpenAI’s supported languages</a></p></li><li><p><a href="https://ai.google.dev/gemini-api/docs/models#supported-languages">Gemini’s supported languages</a></p></li></ul></div></div></td></tr><tr><td><p>Polling Limits</p></td><td><div><div><p>10-second interval for retrieving results<br>Applications must avoid polling for results more often than every 10 seconds.</p></div></div></td></tr><tr><td><p>Checkboxes</p></td><td><p>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. For more information about model performance when processing checkboxes, see <a href="https://docs.mulesoft.com/idp/supported-models">Supported Models</a>.</p></td></tr><tr><td><p>Location Callouts</p></td><td><div><div><p>40 fields and table cells combined<br>Location callouts support a maximum of 40 fields, including table cells. Each table cell counts as a field. Enable this feature if your document action contains 40 or fewer fields and table cells combined.<br></p></div><div><div data-type="IMPORTANT"><div><p>Enabling location callouts on documents larger than 50 pages impacts extraction performance. For optimal performance on large documents, disable location callouts unless specifically required for your use case.</p></div></div></div></div></td></tr></tbody></table>

## 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](https://docs.cloud.google.com/vertex-ai/generative-ai/docs/multimodal/image-understanding)

- [OpenAI: token usage estimation for images](https://developers.openai.com/api/docs/guides/images-vision)

## Automation Credit Consumption and Estimation

IDP consumes Automation Credits per execution, based on the number of pages in the submitted
document. Every execution counts toward consumption, including resubmissions of the same document,
retries of a failed or partially failed execution, and reprocessing runs. IDP doesn’t deduplicate
submissions or discount credits for documents that were already processed.

To estimate Automation Credit consumption, use the following formula:

`(number of submissions) x (pages per document) x (credits per page)`

Count every submission, not only unique documents. For example, if you submit 100 invoices with 2
pages each, and 20 of those invoices are resubmitted once due to retries, the total number of
submissions is 120, not 100.

For the current credits-per-page rate, see
[Automation Credits Usage and Rates](https://docs.mulesoft.com/general/automation-credits-usage-and-rates).

## 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 two regions: US East (Virginia) and EU Central (Frankfurt, Germany). IDP stores the data
closest to your Anypoint control plane region to ensure GDPR compliance. For example, if your
Anypoint control plane runs in the EU region, IDP stores your data in the EU Central (Frankfurt,
Germany) data center.

For a list of supported regions and their corresponding API endpoints, see
[Supported Regions](https://docs.mulesoft.com/idp/automate-document-processing-with-the-idp-api#supported-regions).

## See Also

- [Automation Credits Usage and Rates](https://docs.mulesoft.com/general/automation-credits-usage-and-rates)

- [Supported Models](https://docs.mulesoft.com/idp/supported-models)