Add Orchestration Failure Reporting User Interface

[daniel-slaugh]

The functional spec requires that users can clearly see when orchestration jobs fail, understand why they failed, and quickly navigate to the relevant logs and configuration needed to resolve the issue.

General Requirements

• Orchestration execution status is visible in the Data Management UI
• Failure reporting is scoped to the workspace
• Failure reporting respects workspace permission levels
• Users can identify when a scheduled task has failed or requires intervention

Frontend Requirements

• Display orchestration execution status in relevant UI views
• Clearly indicate failed executions
• Provide a view for inspecting failure details for a specific execution
• Failure details include enough context to isolate the task and examine logs:
  • Workspace
  • Data connection
  • Task
  • Execution timestamp
  • Failure reason or error summary
  • Log reference or identifier
• Provide navigation from a failure to associated log information
• Failure information is readable and does not require viewing raw backend logs

Permissions

• Users can only view orchestration failures for workspaces they have access to
• Failure visibility aligns with existing workspace permission rules
• Sensitive system details are not exposed beyond what is required to isolate and debug the task

Backend Requirements

• Persist orchestration execution status and failure metadata
• Expose execution status and failure information via API endpoints
• Provide stable identifiers for tasks and executions to support UI navigation
• Provide sufficient structured failure data to support UI display and log correlation

Requested features

• Adel thought it would be nice to have the full URL that was called for a specific task at run time, so he could just click it and it would give him the actual file that was returned from the data source.