Configure Error Monitoring for Salesforce
Browser Error Monitoring
Categorize Salesforce Errors
Visualize and Analyze Salesforce Errors
Configure Error Monitoring for Salesforce
GermainUX detects, classifies, prioritizes, and analyzes errors affecting Salesforce users and business processes.
- Which Salesforce errors affect users?
- Which errors are new?
- Which errors recur most frequently?
- How many users, sessions, and workflows are affected?
- Which errors prevent users from completing their work?
- What actions occurred before the error?
- Is the cause related to the browser, Salesforce, Apex, an API, or an integration?
- Has the error stopped occurring after the fix?
Error Sources
GermainUX can detect Salesforce errors from multiple sources.Error Classification
Before configuring dashboards and alerts, distinguish the following categories.userError. In this context, it generally identifies an error relevant to the user experience. It should not be interpreted as proof that the user caused the problem.
Prerequisites
Before configuring Salesforce Error Monitoring, confirm that:Configure Browser and User-Facing Error Monitoring
Open the Salesforce UX Monitoring Profile
In GermainUX Workspace, navigate to: GermainUX Workspace → Left Menu → Settings → Analytics → UX Monitoring Profiles → Salesforce
Profile Capabilities
The current Salesforce profile should provide the applicable configuration for:- Salesforce-specific browser integration
- User and session identification
- Salesforce application and component metadata
- Console
errorandwarnevents - Salesforce Aura errors
- Application and developer errors
Show all 13
Show all 13
- Error toasts and form-level errors
- Network processing
- Salesforce request and response processing
- User clicks
- Page and interaction performance
- Session termination on logout
- Search and workflow monitoring when configured
Recommended Profile Settings
Review the following behaviors in the profile.Browser Log Threshold
Configure which browser log levels should generate facts. A typical Salesforce profile emits:Session End Markers
Configure logout labels so GermainUX closes the user session when the user logs out. Example:User and Application Metadata
Configure metadata providers for attributes such as:- Session ID
- Username or anonymized user identifier
- Salesforce application
- Active Salesforce component
- Business object
- Page or view
- Organization and environment
Console Errors and Warnings
Enable processing for:- An actionable error
- A relevant warning
- Known noise
- Sensitive and requiring sanitization
Salesforce Error Dialogs and Toasts
The Salesforce integration can detect events such as:- Aura application messages
one:applicationError- Lightning developer errors
force:showToasterror messages- Form-page errors
- Validation dialogs
- Other supported Salesforce popup events
- Error name
- Title
- Message
- Stack trace
- Business-object identifier
- User-facing status
- Salesforce component
- Timestamp
Network Errors
The Salesforce profile can process Aura and other Salesforce network activity. Review:- Excluded URLs
- Failed-status handling
- Request and response parsing
- Sensitive-body exclusions
- Duplicate-request detection
- Salesforce-specific request names
- Correlation identifiers
Duplicate Request Detection
The profile can identify repeated network requests within a short period. This may reveal:- Retried failed actions
- Loops
- Duplicate submissions
- Repeated component requests
- UX frustration
Activate and Validate the Profile
After modifying the Salesforce UX Monitoring Profile:Save the profile
Confirm that it is assigned to the Salesforce application
Reload Salesforce in a supported browser
Start a new monitored session
Trigger a safe, known error in a non-production environment
Confirm that GermainUX captures the error
Verify its name, message, user-facing status, session, and application metadata
Open Session Replay and confirm that the error appears in context
Configure Server-Side Error Sources
Browser monitoring reveals what the user experienced. Configure the Engine-based Salesforce sources to add technical evidence.- A Salesforce UI problem
- Custom JavaScript
- Apex code
- SOQL or database activity
- Salesforce platform behavior
- An external integration
- A network or browser problem
- User validation rather than a technical failure
Categorize Salesforce Errors
Without categorization, dynamically changing values can cause the same underlying error to appear as many unrelated messages. For example:Create a Categorization Rule
Navigate to: Analytics → Categorization Then:Create or select a categorization configuration
Select the error KPIs to which the rule applies
Configure the fuzzy-matching threshold
Add filters limiting the rule to Salesforce error facts
Define exact-match prefixes or parsing logic for known dynamic messages
Save the rule
Test it against representative errors
Reprocess historical data when appropriate

Simple Categorization Example
Recommended Salesforce Error Patterns
Common patterns that may require normalization include:An internal server error has occurred Error IDInvalid date formatSendEmail failed. First exception on row 0Unable to get actions for recordIdsUpdate failed. First exception on row 0 with idUpsert failed. First exception on row 0 with id
Show all 12
Show all 12
Record ID is malformedThis record was modified byUnexpected Response codeYou do not have access to the Apex class namedYou do not have the level of access necessary- Messages containing changing
gackIdvalues
- Required fields
- Invalid email addresses
- Missing approvers
- Permission guidance
- Instructions to use a workflow button
Recommended Categorization Logic
A reusable rule can normalize known error prefixes and use a checksum for messages that do not match a known pattern.Existing and New Errors
After categorization:- A known matching error receives an existing category ID.
- A message that does not match an existing category receives a new category ID.
- New categories can trigger alerts or review workflows.
- Recurring occurrences can be aggregated and ranked together.
Visualize and Analyze Salesforce Errors
Create an error-analysis portlet using the KPIs that capture your Salesforce error sources.
Suggested KPIs
Depending on the configuration and GermainUX version, use:- Browser Event
- JavaScript Console Event
- JavaScript Popup Dialog
- Outbound HTTP Request
- Apex exception KPIs
- Salesforce Debug Log KPIs
- Other custom Salesforce error KPIs
JavaScript Popup Dialog is particularly useful for errors displayed through Salesforce dialogs and toasts.
Suggested Measures
Use measures such as:- Count
- Unique error categories
- Unique users
- Unique sessions
- Affected workflows
- Total duration
Show all 9
Show all 9
- Lost productivity
- Failure rate
- Percentage of sessions affected
Suggested Pivots
Use available dimensions such as:- Category ID
- Name
- Message
- Error source
- Application
- Salesforce component
Show all 15
Show all 15
- User
- Profile
- Page or view
- Business process
- Business-process step
- Salesforce organization
- Environment
- Browser
- Application version
Suggested Filter
For configurations using the legacy internal marker, filter on:Include or Exclude Specific Errors
After creating the portlet, add filters to:- Include only user-facing technical errors
- Exclude known benign messages

Filter in or out specific Salesforce errors - GermainUX
- Separate user validation
- Focus on one workflow or Salesforce component
- Analyze only new categories
- Exclude test users or non-production environments
- Limit analysis to critical errors

Configure Alerts and Reports
Immediate Alerts
Configure an alert when:- A new error category appears.
- A critical user-facing error occurs.
- Error volume exceeds a baseline.
- An error affects multiple users.
- A business-critical Salesforce workflow fails.
- A previously resolved error returns.
- Failure rate increases after a deployment.
- An integration error blocks Salesforce users.
Scheduled Reports
Create scheduled reports showing:- New error categories
- Highest-volume errors
- Most affected users
- Most affected workflows
- Error trends
- Resolved and recurring errors
Show all 9
Show all 9
- Errors introduced after a release
- User validations requiring UX improvement
- Estimated productivity or business impact
Validate Error Monitoring
Test the configuration using representative controlled scenarios. Verify that:- A Salesforce error dialog is captured.
- An error toast is captured.
- Browser console errors are captured.
- Failed Salesforce requests are identified.
- Apex exceptions appear when server-side monitoring is enabled.
- Error messages are categorized correctly.
Show all 13
Show all 13
- User validation is separated from technical failures.
- Known benign events are excluded or suppressed.
- New errors receive new category IDs.
- User, application, page, and workflow context are present.
- Session Replay shows the events leading to the error.
- Alerts and reports include only the intended errors.
- Sensitive values are masked or excluded.
No Errors Appear
If known Salesforce errors are missing:Confirm that the RUM Extension is installed and active
Confirm that the Salesforce UX Monitoring Profile is assigned
Verify the application and profile names
Confirm Salesforce CSP Trusted Sites
Check browser connectivity to GermainUX
Verify that console, popup, and network monitoring are enabled
Check whether the error occurs inside an unmonitored or isolated context
Review privacy, exclusion, and filtering rules
Confirm that the selected dashboard time range and environment are correct
For server-side errors, verify the Engine, OAuth, and applicable Salesforce monitors
Too Many Errors or Too Much Noise
If dashboards contain too many non-actionable events:Raise the browser log threshold
Exclude known noisy endpoints
Improve Salesforce-specific error processing
Categorize dynamic messages
Separate validation messages
Exclude recognized benign categories
Alert only on new, critical, or high-impact errors
Rank issues by affected users, workflows, and business impact rather than raw count alone
Security and Privacy
Salesforce error messages can contain:- User identifiers
- Salesforce record IDs
- Customer or patient information
- Field values
- Request and response content
- Stack traces
- Integration endpoints
- Internal implementation details
- Configure masking, anonymization, and exclusions.
- Restrict access to error details and Session Replay.
- Avoid collecting credentials, tokens, and session identifiers.
- Review request and response-body collection.
- Apply appropriate retention policies.
- Validate the configuration with Salesforce security and privacy owners.
Related Documentation
Dashboard & Reports
AI
Analytics
Automation
Get Help
Contact GermainUX Support
Can't find what you need?
The content of this document is proprietary to GERMAIN SOFTWARE.

