Allow users to click on the “Error” icon in workbook schedule result and see results

Martin_Gibbs_Mayo

As an Oracle FDI admin or analyst
I want to click the “Error” icon on a failed workbook schedule result and see the same contextual failure information that BI Publisher provides (e.g., “timed out,” “record count exceeds threshold,” “email delivery failed”)
So that I can quickly troubleshoot and resolve scheduling issues directly within the FDI interface, without needing to access OCI logs or external tools.

Business Value & Use Case

Reduces time to resolution: Users can immediately identify failure reasons without hopping into OCI logs.

Empowers self‑service troubleshooting: Administrators and analysts don’t need to involve DevOps or open support tickets just to get basic error context.

Improves transparency: Having inline error details builds confidence and improves monitoring for scheduled workbooks.

Current Behavior

Users see a clickable “Error” icon when a scheduled workbook fails.

Clicking the icon does nothing—no details, no action.

To find out why a schedule failed, users must access OCI tenancy logs (e.g., audit, scheduler, or BI Publisher logs).

Desired Behavior:

Click Error icon → UI pops up with error details.

Error details should include BI Publisher‑style messages:

Timeout events

Record‑count threshold violations

Delivery failure reasons (e.g. SMTP issues)

This enhancement bridges visibility gaps between scheduled workbook execution and actual failure reasons. It aligns FDI with user expectations common in BI Publisher—and streamlines incident resolution processes. Users shouldn’t have to leave the interface just to know what went wrong. This also cuts support ticket volume and boosts operational efficiency.