Use the Fullcast Policy Error Logs to diagnose issues with policy execution, especially when a Fullcast Policy Status record is missing, incomplete, or shows a failure that requires deeper investigation. This applies to all policies including routing (such as lead routing and account routing), holdouts, etc.
Prerequisites
Salesforce Administrator access or appropriate permissions to view logs and potentially related Fullcast settings.
Familiarity with the expected behavior of the Fullcast policy you are troubleshooting.
Understanding of how to interpret standard Fullcast Policy Status records.
When to use error logs
While the Fullcast Policy Status record provides comprehensive details on policy execution, Fullcast Policy Error Logs are crucial in specific troubleshooting scenarios:
A Fullcast Policy Status record is not generated for a policy that you expected to execute.
A Policy Status record shows a Failure status, but the information in the Input, Process, or Output sections is insufficient to determine the root cause.
A policy appears to have been triggered but not complete, and no Policy Status is available.
How to access Fullcast policy error logs
The exact method for accessing Fullcast Policy Error Logs needs to be confirmed within your specific Salesforce instance. The following are common patterns in Salesforce. Please verify and use the correct steps for your organization. Update this section with precise instructions and screenshots once confirmed.
Via a custom object tab
If Fullcast provides error logs as a custom object with a dedicated tab:
Look for a tab in your Salesforce apps named something like Fullcast Error Logs, Policy Error Logs, or similar.
If the tab is not visible, you may need to customize your navigation bar or check App Launcher:
Click the App Launcher (icon resembling a grid of dots).
Type "Error Logs" or "Fullcast" in the search box to see if a relevant item appears.
Via the custom object records
If a tab is not configured, you might access records directly through Setup.
In Salesforce, Navigate to Setup > Object Manager.
Search for a custom object named Fullcast Policy Error Log
Click on the object name.
Go to the Fields & Relationships section to understand the data captured, and then look for a button or link like Manage [Object Name] or go to a list view for that object (you might need to create one).
Once you have located the error logs, you can typically view them as a list. You may need to create or adjust list views to show relevant fields and filter by date/time to find specific errors.
Interpreting error logs
Fullcast Policy Error Logs will typically contain technical information about exceptions or problems encountered during policy processing. Key fields include:
Created Date: When the error occurred.
Error Log Number: Unique identifier for the specific error log record.
Error Type: This could be GovernorLimits, Debug, System.AsyncException, System.DmlException, MoveAccounts.ApplicationException, System.SObjectException
Error Message: A summary of the error.
Comma Sep Params: Records the sequence and values of important internal data at various stages of a Fullcast operation. This includes logging the values of collections (like maps and sets), parameters passed between functions, constructed SOQL queries, and the size or contents of data structures. This detailed logging is primarily used for technical troubleshooting and debugging, allowing administrators or developers to understand the data context and logic flow leading up to an error or unexpected behavior.
Class Name: The policy that was attempting to run.
Common troubleshooting steps based on policy error logs
Identify the Timeframe: Filter logs to the time the issue was reported or observed.
Look for Specific Record IDs: If the issue pertains to a particular Lead or Account, you can search the Comma Sep Params field for the record ID.
Analyze Error Messages:
Search online for common Salesforce error codes or messages.
Check for issues related to permissions, data validation rules, or limits (e.g., SOQL query limits, CPU time limits).
Look for messages indicating problems with Fullcast configuration or connectivity.
Correlate with Policy Status: If a Policy Status record was generated with a Failure, compare its timestamp with error log entries.
Relationship to policy status
Typically, error logs capture issues that prevent a normal Fullcast Policy Status from being fully generated or provide deeper technical details for a failure status.
Impact of debug mode on log volume
Enabling Salesforce debug logs (via Setup > Debug Logs) or any specific Fullcast-internal debug modes can dramatically increase the number of entries in Fullcast Policy Error Logs, and potentially in Salesforce Apex logs. This can include very verbose logging for even a single action. While extremely useful for granular, step-by-step troubleshooting by developers or support, it can also quickly consume log storage limits and make it harder to find critical errors among the noise.