Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Oracle Apex v20.2 Debug feature

Srini-SJan 9 2022

Whenever I enable debug during development, the page reloads and the debug begins. In order to see what the page did during loading / rendering, I need to verify many debug ids at times. Whichever debug has more entries is what I usually pick to drilldown to see the issue.
Question: Why are there so many debug ids created? Shouldn't it be just one that gets created when I Just enabled? What controls this behavior of number of debug ids? Is it the maximum lines in a given single debug view id as set up in some configuration? Or the way the code is written when the page is connecting, disconnecting with server? There are times like when I had to search 10-15 view ids before I could locate the problematic code. Even if I want to go by the creation time, all debug codes are created at the same time like '5 seconds ago', '10 seconds ago' etc. Is there an easier way to pick the actual debug id that's most recent and has all that the page did during loading/rendering ?
Once page is loaded, there may be actual transactions that create additional debug entries and if I need to look at those as, that's more problematic too. What am I missing?

This post has been answered by fac586 on Jan 9 2022
Jump to Answer
Comments
Post Details
Added on Jan 9 2022
5 comments
386 views