Over the past six months working in Frappe Framework Customer Support, I have investigated and resolved nearly 250+ tickets across different Frappe and ERPNext installations. A consistent pattern I observed is that many issues can be diagnosed quickly using simple but powerful tools such as browser developer tools, stack traces, and Python debuggers.
Debugging issues in Frappe applications often takes longer than necessary, not because the problems are complex, but because many developers underuse the tools available to them.
In this session, I will walk through practical debugging workflows that developers can use in day-to-day development. Using real examples inspired by support tickets (of course I won't reveal customer details, lol), I will demonstrate how to trace issues from the user interface to the server side and identify the root cause quickly.
Topics covered will include:
- Using Chrome DevTools to inspect UI elements and identify the JavaScript functions attached to them
- Tracing client-side errors through network calls and stack traces
- Temporarily overriding JavaScript in the browser to isolate custom scripts or conflicting logic
- Attaching debuggers in JavaScript and Python (
pdb) to step through execution
The goal of the talk is to share a set of practical techniques and tools that can be used to debug Frappe based apps.

