Diagnostic Console visibility boundaries for granular rollback error diagnostics in Fusion deployments

In current Oracle Fusion Cloud Applications releases, deployment failures can surface as generic Service Unavailable or Timeout responses in the UI while the Diagnostic Console reports only high-level service health without exposing underlying stack traces or specific database errors that triggered the rollback. Administrators relying on periodic log exports through the support interface face the risk that automated retention purging deletes relevant WebLogic managed server entries before manual investigation begins.

The unresolved behavior concerns whether rollback error granularity is fixed by design, governed by a configurable diagnostic setting, or restricted by a permission boundary separating UI-visible health status from backend log detail. Security policies that mask PII and system metadata further complicate data-dependent failure diagnosis, leaving uncertainty about what error detail is intentionally withheld versus available through a specific configuration path. Because documented behavior can vary across Fusion Cloud update cycles, the exact boundary between visible health status and accessible log detail may require confirmation against current release documentation.

Which configuration or permission boundary controls the visibility of granular stack traces and unmasked database error codes during a failed deployment rollback in Fusion Cloud? Does the Diagnostic Console expose a documented setting to increase error-code granularity beyond high-level service health, or is deeper log access strictly limited to periodic exports? How do automated retention windows interact with the time required to request and receive those exports when diagnosing a masked rollback failure?