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 Limits
Apex Debugger Considerations
Apex Debugger Troubleshooting
Get Started with the ISV Customer Debugger
Solutions to Common Force.com IDE Problems
Force.com IDE Release Notes
Useful References
PDF

Apex Debugger Limits

Your use of the Apex Debugger is subject to these restrictions.
  • You can debug only sandbox orgs.

    The Apex Debugger implementation for Eclipse works only with sandbox orgs. To debug scratch orgs, install Apex Debugger for Visual Studio Code.

    Note

  • You can have only one active debugging session per org across all the org’s sandboxes. However, you can purchase more sessions for your parent org. Each sandbox org can have only one active session.
  • You can’t debug more than two threads at a time.
  • Your Apex Debugger session times out if it’s left inactive. Under normal conditions, you’re allowed 1 hour of inactivity. When your instance’s server is experiencing peak loads, the timeout limit can be reduced to 30 minutes.
  • Your Apex Debugger session times out after 4 hours, regardless of activity.
  • Salesforce can terminate debugging sessions for maintenance purposes, with or without notice. You can’t initiate a new debugging session until the maintenance is complete.