You are here:
Loyalty Management Process and Configuration Limits
Review the loyalty program-specific recurring process limits and loyalty program process rule configuration limits.
Process Limits
| Limit | Default Limit | Extendable | What it Means for Real-Time Processing | What it Means for Batch Processing | Example | Workaround |
|---|---|---|---|---|---|---|
| Number of transactions that can be created and processed in a single request | 1,000 | No | The Transaction Journal Execution API can create and process up to 1,000 transaction journals in a single POST request. |
|
In a single request, transaction journals for up to 1,000 order lines and member activities combined can be created and processed. | Process transactions in near real-time by splitting transactions into groups of up to 1,000 in the middleware that connects transaction source systems with Salesforce, and then execute Transaction Journal Execution API for each group. |
| Number of transactions that can be created and processed in an hour | 3.5 million | Yes | The Transaction Journal Execution API can create and process up to 3.5 million transaction journals in a hour. |
|
In an hour, transaction journals for up to 3.5 million order lines and member activities combined can be created and processed. | If you need to create and process more than 3.5 million transactions every hour, contact Salesforce Customer Support. |
| Number of times processes that can be executed to create and process transactions in an hour | 500,000 | No | The Transaction Journal Execution API can be executed up to 500,000 times in a hour to create and process transaction journals. |
|
In an hour, up to 500,000 times processes can be executed to create and process transaction journals for order lines and member activities. | Process transactions in near real-time by grouping up to 1,000 transactions in the middleware that connects transaction source systems with Salesforce, and then execute Transaction Journal Execution API for each group. For example, if orders have four line items at an average, group the transactions for 100 orders and then execute the API with 400 transactions for the 100 orders. |
Number of POST requests that can be executed for business APIs in a hour This limit doesn't count against the hourly limit for the Transaction Journal Execution API. |
500,000 | No | POST requests can be executed for these business APIs up to 500,00 times combined in an hour:
|
Not applicable, business APIs are always executed in real-time. | In an hour, all members combined can perform up to 50,000 activities that execute these APIs. For example, if a member performs one activity in a hour, up to 50,000 members can each perform one activity. |
Process member activities in near real-time by grouping activities in the middleware that connects external systems with Salesforce, and then execute APIs for activity groups. For example, execute the Issue Voucher API for a group of members who must be issued a voucher rather than executing the API for one member at a time. |
| Number of GET requests that can be executed for business APIs in a hour | 500,000 | No | GET requests can be executed for these business APIs up to 500,00 times combined in an hour: |
Not applicable, business APIs are always executed in real-time. | In an hour, all members combined can perform up to 50,000 activities that execute these APIs. For example, if a member performs one activity in a hour, up to 50,000 members can each perform one activity. |
On external systems where members manage their profile or perform activities such as redeeming points, build a caching mechanism to reduce the number of times the configurable business APIs are executed in Salesforce. |
| Number of times decision tables can be run in an hour | 450,000 | Yes | Decision tables can be run up to 450,000 times per hour for across all processes. | Decision tables can be run up to 450,000 times per hour for across all processes. | Batch processes can run decision tables up to 450,000 times per hour. |
|
Number of times members can redeem points with traceability in an hour This limit is only applicable for orgs where the Trace Usage of Points setting is tuned on. |
250,000 | Yes | The Transaction Journal Execution API can create and process up to 250,000 Debit type transaction journals in a hour. |
Not applicable, redemptions are always processed in real-time. | In an hour, transaction journals for up to 250,000 order lines and member activities combined where members have redeemed points can be created and processed. | If you need to process more than 250,000 member redemptions every hour, contact Salesforce Customer Support. |
Number of non-qualifying point accrual ledgers available for each member with traceability This limit is only applicable for orgs where the Trace Usage of Points setting is tuned on. |
2,000 | Yes | Not applicable | Not applicable | Before admins turn on the Trace Usage of Points setting, members can't have more than 2,000 Credit type loyalty ledgers associated to them for each non-qualifying currency. | If you already have members who have reached this limit, see Implementation Guardrail for Loyalty Member Transactions in Spring '25. |
Loyalty Program Process Rule Configuration Limits
| Limit | Default Limit | Extendable Limit |
|---|---|---|
| Number of active promotions associated with rules | 200 | No |
| Number of active rules in a process | 200 | No |
To request an increase of one of the extendable limits in your org, see How to create a case with the Feature Activations & Limits Team.
