DEVOPSdigest

Gearset announced the expansion of its new Observability functionality to include Flow and Apex error monitoring.

This new addition is designed to give Salesforce DevOps teams better visibility into the health and behavior of their orgs. By surfacing and analyzing Flow and Apex errors in real time, teams can now catch issues early, troubleshoot faster, and protect critical business processes from costly disruptions.

"Observability has long been a blind spot in Salesforce DevOps, and it's time that changed," said Matt Dickens, co-founder and Chief Product Officer at Gearset. "We're giving teams the tools to move from reactive troubleshooting to proactive monitoring. With Flow and Apex error monitoring, you don't just know that something's broken - you know why, where, and how to fix it before it affects users."

Salesforce Flows and Apex code play a pivotal role in automating complex logic across the platform. But when they fail unexpectedly, often due to data anomalies or system changes, they can disrupt or block key business processes.

With Flow and Apex error monitoring, Salesforce teams can now see every Flow and Apex error in one centralized dashboard. Key insights about org health are surfaced, such as total users impacted over time, the most common error types, the top 10 Flows with errors, as well as the total number of errors.

Errors can be filtered by type and drilled into for additional details, including visualizing where within the Flow the error occurred. This helps teams diagnose root causes faster and make smarter decisions about where to focus development efforts. Customizable alerts in Slack or Microsoft Teams stop critical issues from getting buried in an inbox, and ensure that teams are only notified for what they care about, such as when issues exceed defined thresholds.

"Being able to proactively catch and understand Flow and Apex errors is a game changer,"  said Ben Laplanche, VP of Product at Gearset. "Insights from Gearset's Observability solution will also feed into planning for future development cycles, helping teams to see how their efforts are impacting org health and make more strategic decisions."