skills.rest
forcedotcom
forcedotcomOFFICIAL
Explore all skills by this author →
Website𝕏@salesforcedevsGitHub

debugging-apex-logs

Analyze Salesforce Apex debug logs to identify root causes of runtime failures and governor-limit bottlenecks.

803|289|Updated Nov 7, 2025
Search Tags:#debugging#root cause analysis#stack trace#performance profiling#governor limits#apex logs#soql in loop
One-click install
npx skills add https://github.com/forcedotcom/sf-skills --skill debugging-apex-logs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-apex-logs
Source: https://github.com/forcedotcom/sf-skills/tree/main/skills/debugging-apex-logs
Command: npx skills add https://github.com/forcedotcom/sf-skills --skill debugging-apex-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Apex teams waste time guessing why code fails or burns governor limits; this skill helps you pinpoint the evidence-backed root cause directly from Salesforce debug logs.

Core Features & Use Cases

  • 100-point log scoring to prioritize what to fix first and how severe each issue is.
  • Governor limit detection for SOQL, DML, CPU, and heap pressure using LIMIT_USAGE signals.
  • Stack trace interpretation to map exceptions back to the originating class, method, and transaction stage.

Quick Start

Use debugging-apex-logs to analyze the latest Apex debug log for AccountTrigger performance issues in org dev and produce prioritized, evidence-based fixes.

Frequently Asked Questions about debugging-apex-logs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of a Salesforce Apex governor limit error from debug logs?▼

To find the root cause of an Apex governor limit error, analyze debug logs for LIMIT_USAGE signals and SOQL/DML markers to identify bulk-safe bottlenecks. This skill scores log severity to pinpoint the exact transaction stage causing the failure.

What do FATAL_ERROR and EXCEPTION_THROWN events mean in an Apex stack trace?▼

FATAL_ERROR and EXCEPTION_THROWN events in an Apex stack trace indicate runtime failures mapped back to the originating class and method. Interpreting these debug log events classifies exception severity and isolates the failing transaction stage.

How do I identify SOQL in loop patterns causing CPU and heap pressure in Apex logs?▼

Identify SOQL in loop patterns causing CPU and heap pressure by examining debug logs for repetitive SOQL/DML markers and LIMIT_USAGE events. This analysis isolates performance hotspots and recommends the smallest correct bulk-safe fix.

Can I use Apex debug logs to troubleshoot AccountTrigger performance issues in a developer org?▼

Yes, you can use Apex debug logs to troubleshoot AccountTrigger performance issues in a developer org. Analyzing log evidence like LIMIT_USAGE and stack traces produces prioritized, evidence-based fixes for governor limit bottlenecks.

What is the best way to prioritize which Apex log failures to fix first?▼

The best way to prioritize Apex log failures is applying a 100-point log scoring system to evaluate severity. This targets troubleshooting scenarios by interpreting FATAL_ERROR and LIMIT_USAGE events to classify the most critical issues.

Related Skills

Explore More Software Engineering Skills→
ronitnugururonitnuguru
6

sf-debug

Analyze Salesforce Apex debug logs for governor limits and performance bottlenecks.

Community
Advanced
JaganproJaganpro
423

sf-debug

Diagnose Salesforce Apex debug logs to identify governor-limit violations and root causes.

Community
Advanced
david-sfdevdavid-sfdev
6

apex-development

Review Salesforce Apex code for compliance with NimbleUser Apex Style Guide rules.

Official
Advanced
angryracoonangryracoon

platform-apex-logs-debug

Analyze Salesforce Apex debug logs to diagnose failures and governor-limit breaches.

Community
Advanced