Salesforce Docs Portal

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

  • 150 pages per file

  • 15 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) or GPT-4o Mini (gpt-4o-mini)

  • Approximately 48,000 output words for Einstein prompts using Einstein GEMINI-3.5

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

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:

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. For more information about model performance when processing checkboxes, see Supported Models.

Location Callouts

40 fields and table cells combined
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.

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.

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:

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.

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.

See Also