Critical Issue:
In our large-scale environment, the "Show Descendants" parameter creates significant stability risks. When enabled, it bypasses the Depth of Descendants limit, allowing any user to trigger recursive rendering of massive page hierarchies.

The Risk at Scale:
With thousands of users, "unbounded" macros frequently cause performance spikes, browser hangs, and instance instability. As admins, we lack proactive controls to prevent these resource-heavy queries before they impact the wider community.

Requested Solution:

• Global Depth Cap: An administrative setting to enforce a maximum depth that overrides the "Show Descendants" parameter.
• Toggle Governance: The ability to disable the "Show Descendants" (unlimited) option for end-users, forcing a defined numerical depth.
• User Notification: When a limit is hit (depth or child count), the macro should display a built-in message explaining that the view is restricted for performance reasons.

Impact:
This shifts our strategy from reactive troubleshooting to automated limits. It ensures platform stability while providing transparent feedback to our users when they hit system boundaries.