Force.com IDE Developer Guide

Get Started with the Force.com IDE
Develop with the Force.com IDE
Test Code with the Force.com IDE
Deploy Code with the Force.com IDE
Get Started with the Apex Debugger
Get Started with the Apex Debugger
Set Up the Apex Debugger
Explore a Simple Debugging Puzzle
Manage Debugging Sessions
Apex Debugger Limits and Considerations
Apex Debugger Troubleshooting
Relaunch Your Debug Configuration
Kill an Orphaned Session
Change Your Session Timeout Preference
Report Drastic Issues to Customer Support
Get Started with the ISV Customer Debugger
Solutions to Common Force.com IDE Problems
Force.com IDE Release Notes
Useful References
PDF

Report Drastic Issues to Customer Support

It’s unlikely that you’ll encounter drastic issues while working with the Apex Debugger. However, never say never. If you encounter performance issues or are unable to kill your orphaned sessions, contact Salesforce Customer Support for help. If necessary, Support can kill all debugging sessions for the instance on which your org is running. This process prevents you—and all orgs running on your instance—from immediately initiating new debugging sessions.

Force.com IDE is in a maintenance-only state. We still provide support for the product through our official channels, but updates prior to October 12, 2019 will be only for critical security issues that arise. On October 12, 2019, we will no longer provide support or updates of any kind for Force.com IDE. On that date, we will also begin archiving documentation and removing download links for the product. We recommend that you start migrating to Salesforce Extensions for Visual Studio Code or one of the great tools made by our partners. For more information, see The Future of Salesforce IDEs on the Salesforce Developers Blog.

Warning