Force.com IDE Developer Guide
Winter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
Summer '21 (API version 52.0)
Spring '21 (API version 51.0)
Winter '21 (API version 50.0)
Summer '20 (API version 49.0)
Spring '20 (API version 48.0)
Winter '20 (API version 47.0)
Summer '19 (API version 46.0)
Spring '19 (API version 45.0)
Winter '19 (API version 44.0)
Summer '18 (API version 43.0)
Spring '18 (API version 42.0)
Winter '18 (API version 41.0)
Summer '17 (API version 40.0)
Spring '17 (API version 39.0)
Winter '17 (API version 38.0)
Summer '16 (API version 37.0)
Spring '16 (API version 36.0)
Winter '16 (API version 35.0)
Summary of Getting Started with the Apex Debugger
Relaunch Your Debug Configuration
Kill a Debugging Session in Setup
Kill a Debugging Session with the Tooling API
Change Your Session Timeout Preference
Report Drastic Issues to Customer Support
Kill an Orphaned Session
If Eclipse crashes or is shut down before you end your debugging
session, your session is orphaned. You can’t start a new session until you remove the
orphan. But don’t panic! You can kill an orphaned session in Setup or with the Tooling API.
-
Kill a Debugging Session in Setup
From the Apex Debugger page in Setup, you can easily kill any debugging session in your org—even sessions belonging to your coworkers. Please use this power compassionately! -
Kill a Debugging Session with the Tooling API
If you’re too cool for declarative tools, fret not: You can kill a debugging session using the Tooling API, without going anywhere near the Setup tree.