Glade Help
Fix a problem
Start with the symptom. Diagnose the same project and selected local environment before changing source or resetting data.
| What happened | First safe check | Continue with |
|---|---|---|
| Command not found | glade version and the install directory on PATH | Installation |
| Project or doctor failure | test -f sfdx-project.json, then read the first failed doctor row | Project recovery |
| No test result or zero tests | Check the JSON total and actual class/method names | Test discovery |
| A breakpoint never stops | Run the selected test without the debugger | Breakpoint recovery |
| A local target is missing | Check the same project, alias, and isolated sf configuration | Local target setup |
| CI loses results | Preserve nonzero exits and upload existing artifacts after failures | CI setup |
| Local results differ from Salesforce | Name the capability, local result, and hosted boundary | Compatibility |
Open all troubleshooting paths
Complete a task
Use Guides for the main task paths. These illustrated walkthroughs retain interface-specific steps and recovery details.
Run the first local checkOutcome: a configured project and a checked source tree.
Interface: terminal.Run one Apex testOutcome: focus a local test loop on one class or method.
Interface: terminal and VS Code.Debug Apex with breakpointsOutcome: stop in a local Apex test and inspect state.
Interface: VS Code.Use anonymous Apex scratchOutcome: execute a local snippet and inspect output.
Interface: VS Code.Work with local dataOutcome: seed and query a local environment.
Interface: terminal.Run changed tests before a PROutcome: select only tests affected by your changes.
Interface: terminal and CI.Profile an Apex debug logOutcome: analyze saved debug-log events locally.
Interface: terminal.Add Glade to CIOutcome: emit a reliable local check, test, and report gate.
Interface: CI.
Interface: terminal.Run one Apex testOutcome: focus a local test loop on one class or method.
Interface: terminal and VS Code.Debug Apex with breakpointsOutcome: stop in a local Apex test and inspect state.
Interface: VS Code.Use anonymous Apex scratchOutcome: execute a local snippet and inspect output.
Interface: VS Code.Work with local dataOutcome: seed and query a local environment.
Interface: terminal.Run changed tests before a PROutcome: select only tests affected by your changes.
Interface: terminal and CI.Profile an Apex debug logOutcome: analyze saved debug-log events locally.
Interface: terminal.Add Glade to CIOutcome: emit a reliable local check, test, and report gate.
Interface: CI.
Check support and trust
Report a bug or share workflow feedback. Include the command, version, OS, expected/actual result, and a minimal public reproduction. Do not upload proprietary source, private package names, credentials, or customer records. Report vulnerabilities through the private security route, not public issues.
Confirm what Glade runs locally and review the release and plugin trust boundaries.
What Glade runs locallySearch supported APIs, named limits, and paths that still require Salesforce.Security & trustVerify releases, checksums, SBOMs, attestations, and plugin execution boundaries.
Use the error reference when output includes a stable Glade error code.