What GermainUX Watches
Find the Cause
Alert and Act
Set It Up
Overview
A release goes out in the morning. An hour later, sales reps say that saving an Opportunity takes ages, and some of them get an error on the pricing panel. The developer has the code open in their IDE, but not what production did: which saves slowed down, which exception was thrown, and on which line. That evidence is spread across Salesforce. Event Monitoring log files, debug logs, the Setup Audit Trail and deployment history each sit on their own screen, and the developer has to download, open and compare them by hand. Meanwhile, the assistant in their IDE can read the code but has never seen production. GermainUX collects all of it, from Apex executions and exceptions to debug logs and deployments. With the GermainUX MCP Server, the developer’s coding assistant reads that data in the same conversation as the code. It finds the deployment that started the slowdown, reads the exception and its stack trace, confirms the cause in the debug logs and opens the line in the repo. It then proposes the fix and, after the hotfix, checks that production is back to normal.Questions It Answers
- Did this morning’s deployment slow down Opportunity saves, and by how much?
- What did the deployment change, and who deployed it?
- Which exception do users hit, and which line of Apex throws it?
- Is it our code, or Salesforce, the network or the pricing API?
- What’s the fix, based on what production actually did?
- Is it fixed?
What GermainUX Watches
The assistant answers from the same KPIs the Workspace shows. The Salesforce Engine monitors collect them through the Salesforce APIs, with nothing to install in the org.Find the Cause
The investigation runs in one conversation, in the IDE where the code is:- Ask what changed in production after the deployment. The assistant compares the slow saves with the same hours on the previous days and lines them up with the deployments and Setup changes.
- Read the exception users hit and its stack trace, down to the class and line.
- Confirm the cause in a debug log: what the execution did, query by query.
- Rule out what stayed normal: other objects, external APIs and Salesforce itself.
- Open the line in the repo and fix it, then ask again after the hotfix to confirm it worked.
Example: A Release Puts a SOQL Query in a Loop
At 08:40 on Friday, Nov 13, a deployment changesOpportunityPricingService, its test class and OpportunityTrigger. Since that release, the service reads the pricebook entry of each line item with its own query. An Opportunity with many products now runs dozens of queries on every save, and the biggest ones hit Salesforce’s limit of 100 queries per transaction. The developer reproduces it with a trace flag on their own user, then opens the SFDX project in VS Code and asks Claude Code.
Ask what changed after the deployment
query_kpi), then Deployment Run and Salesforce Setup Audit for the same morning. In this example, the slowdown comes from one entry point, OpportunityPricingController.recalculate. It takes 5.96 seconds on average and runs 54 SOQL queries per call, against 0.72 seconds and 4 queries on the previous days. The other entry points keep their usual times. Hour by hour, the slowdown starts at 09:00.The match is the Salesforce deployment at 08:40, and the Setup Audit Trail records a changed Apex class and trigger at 08:44. The other releases that morning belong to other applications. Because the repo is open in the IDE, the assistant also names the commit that most likely went out with the deployment, 1b46bb0, which replaced one bulk PricebookEntry query with one query per product.
Slow Saves Since the Deployment - Claude Code

Opportunity Saves Between the Deployment and the Hotfix - GermainUX

Deployment Marker Details - GermainUX
Read the exception
query_kpi). In this example, System.LimitException: Too many SOQL queries: 101 is thrown 6 times, for 4 users. Its stack trace runs from OpportunityTrigger line 12, through OpportunityPricingService.recalculate line 88, to OpportunityPricingService.loadPrices line 214. The assistant finds the users by matching each exception with the Lightning error a user saw at the same moment. When an Opportunity has enough line items to go past 100 queries, the whole save fails.
The Exception and Its Stack Trace - Claude Code
Confirm it in the debug log
query_kpi, search_kpi_facts). In this example, each of the 12 traced saves takes about 5 seconds, almost all of it in OpportunityTrigger on the before-update event. Each one runs 101 PricebookEntry queries, about 40 milliseconds apart, and ends in System.LimitException. Each query is fast. The save is slow, and then fails, because of how many there are. See SOQL Execution for what a debug log records.
101 Queries per Save in the Debug Log - Claude Code
Rule out the rest
query_kpi on Salesforce Log Apex Callout). Each save makes at most one call, so the API accounts for well under a second of the 5 to 6 seconds. Salesforce Instance Status is OK at every check. The 08:40 deployment is the only Salesforce code change that morning. The cause is in the code it changed.
Nothing Else Lines Up - Claude Code
Fix the code
loadPrices in OpportunityPricingService.cls and fix it so a save runs one pricebook query, whatever the number of line items. Show me what the release changed first.”The assistant shows what commit 1b46bb0 changed: it replaced one bulk PricebookEntry query with one query per product, and dropped the IsActive = true filter. The fix reads the prices of every product on the line items, across all the Opportunities in the save, in one query, and restores the filter. recalculate now calls it once, before the loop over the Opportunities. Prices still come from the pricebook at save time, which is what the release wanted:
The Fix, Based on What Production Did - Claude Code
Confirm the fix
LimitException has been thrown since, up to the latest data on Nov 17. In the Workspace, the execution times drop at the hotfix marker on the chart above.
Saves Before and After the Hotfix - Claude Code
OpportunityPricingService. To hover a deployment marker that an exception marker covers, click Salesforce Log Apex Unexpected Exception in the chart legend to hide the exceptions.
Hotfix Marker Details - GermainUX
Alert and Act
Users noticed this release before the team did. To catch the next one sooner:- SLAs and outlier detection on the duration of Apex executions, per entry point, so a release that slows one save raises an alert
- Alerts on new Apex exceptions such as
System.LimitException, by email, Microsoft Teams or Slack - Alerts on Setup changes for Apex code changed in production, so the team knows a release landed
- A post-release check in your IDE: right after each deployment, ask the assistant to compare the classes it changed with the same hours on the previous days
Set It Up
Each step adds value on its own. The assistant can answer more questions the more of the org GermainUX monitors.Monitor the Salesforce org
Collect debug logs
Show deployments on the timeline
Enable the MCP Server for developers
Connect the coding assistant
Additional Resources
MCP Server
Salesforce Engine Monitoring
Use Cases
Get Help
Every Salesforce team has its own release process, trace-flag habits and coding tools. The GermainUX team can help you deploy Salesforce Engine monitoring, bring your deployments onto the timeline, and set up the MCP Server for your developers.Contact GermainUX Support
Can't Find What You Need?
The content of this document is proprietary to GERMAIN SOFTWARE.

