Limits and Considerations for Retail Execution Visit Assistant

Data Volume and Processing Limits

If a data request exceeds system thresholds—typically due to querying information such as orders, visits, customer tasks, or visit jobs over an excessively long timeframe—the assistant doesn’t process the full request.

Data processing is governed by these constraints:

• Apex Governor Limits: The assistant operates within standard Salesforce execution limits (such as SOQL record counts and heap size) when retrieving data.
• Agents Limits: Large volumes of data can exceed the Large Language Model’s (LLM) context window or token capacity.

Outcome of Exceeding Limits:

If your query targets a volume of data that exceeds these limits, the assistant handles them in one of these two ways:

• Returns an error message indicating that the request can’t be completed.
• Provides insights based only on data up to the limit, which can result in a partial view of the requested information.

Data Security and Access

The agent enforces your existing Salesforce data security rules, ensuring users access only the data they’re permitted to view.

• Object-level (OLS) and Field-Level Security (FLS): Users must have the correct permissions for objects and fields to view the Retail Execution data the assistant uses.
• Record Sharing Access: Users must have the correct record-level sharing access to view retrieved data.
• Sales Organization Access Control: The agent retrieves and displays data only if the user's assigned sales organization matches the account's assigned sales organization.