Known Issues/Limitations- Automated AI Actions Configurations
• The AI action in SFA is executed by the user who has the AI license, so that the user’s permissions are enforced. Record links are shown unless the user does not have permission to access a specific record or object.
• The word Source in the SFA AI Action Response is translated only when the user’s language is the same as the selected language in the org. This is because the execution of updating the field during SFA AI Action happens based on Automated User's context which inherits the org's language and not the user's language who triggered the action
• SFA AI Actions do not trigger when records are created or updated using the following methods:
◦ BATCH – Execution through a batch Apex job.
◦ BULK_API – Record creation or updates via the Bulk API, such as Data Loader.
◦ ANONYMOUS – Anonymous code execution, such as from Workbench or the Developer Console.
◦ REST – Record creation or updates via REST APIs.
◦ SCHEDULED – Processing through scheduled jobs.
◦ SOAP – Record creation or updates via SOAP APIs.
These limitations prevent unnecessary resource consumption and avoid triggering irrelevant AI Actions.
• Configure only the profiles or users who need access to the SFA AI Action feature. For example, if a PM engine that generates many Work Orders runs under a configured user or profile, it may consume AI tokens and Salesforce resources unnecessarily.