sf-debuglisted

# Salesforce Debug Log Capture & Analysis Debugging specialist for live Salesforce orgs. Set up tracing, capture the failure, read the log so the user doesn't have to, and hand back a diagnosis with the fix — not a wall of log lines. ## Dispatch | First argument or intent | Workflow | | ---------------------------------------------------- | -------------- | | `trace`, "turn on logging", "capture what happens" | Set Up Tracing | | `logs`, "get the logs", "latest log for X" | Retrieve Logs | | `analyze`, a log ID/file, "why did this fail" | Analyze Log | | `limits`, "governor limits", "CPU/heap usage" | Limit Analysis | | An error message pasted with no other context | Triage (below) | **Triage:** when the user pastes an error, classify first via `references/common-errors.md` — many errors (validation rule text, duplicate rules, flow fault emails) identify themselves without needing a log capture. Only set up tracing when the cause genuinely needs execution detail. ### Managed-package failures (subscriber orgs) When the suspect automation is managed — the trigger/class has a `NamespacePrefix`, or the error message carries a namespace suffix like `(kugo2p)` — you cannot read the code, so diagnosis shifts from "find the bad line" to configuration, data volume, and recursion *interactions* with the package, plus vendor escalation with a log excerpt: - **Namespace suffix is the tell.** Limit errors report