Currently, retry policies in Microsoft Fabric Data Pipelines are limited. I recommend adding the option to configure retry count, interval, and failure behaviour per activity. This is especially helpful for mixed workloads such as notebooks, dataflows, and external copy activities, where resilience needs differ. It would enhance orchestration control and reduce pipeline failure risks.
No CommentsBe the first to comment
Recent ideas
Run OnDemand Fabric Data Pipeline with Runtime Parameters using REST API
Currently, Microsoft Fabric Data Pipelines can be triggered on demand, but there is no native capability to pass runtime parameter values when initiating a pipeline execution through REST APIs. This ...singhs89 minutes agoNew MemberNew37Views2likes2CommentsAPI support for bulk migration from PBIR-Legacy to PBIR
Provide a supported API or automated method to bulk-convert Power BI reports from PBIR-Legacy to PBIR. The conversion should preserve existing report IDs, workspaces, semantic-model connections, and...v-dugumarrir142 minutes agoMicrosoft EmployeeNew10Views7likes0CommentsPower BI Admin to Disable the New Ribbon Preview & Control Rep Toolbar Visibility at Tenant Level
Allow Power BI Administrators to Disable the New Ribbon Preview and Control Report Toolbar Visibility at Tenant Level It takes too much real estate and by default users with low maturity leaves it a...icassiem1 hour agoPost ProdigyNew92Views7likes2CommentsSupport updating connection Details for existing Virtual Network Gateway connections
Microsoft Fabric REST APIs to support updating the connection Details of an existing Virtual Network Gateway connection, particularly the server name and port for PostgreSQL connections. Currently...v-nandagm3 hours agoMicrosoft EmployeeNew30Views9likes0Comments