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
About "Download SQL database project" and fix the downloaded project
1. The sqlproj must be fixed, it is downloaded without the xml markup line <?xml version="1.0" encoding="utf-8"> 2. The sdk must be updated: Actual: <Sdk Name="Microsoft.Build.Sql" Version="0.1...Jarrinf2 days agoFrequent VisitorNew74Views3likes3CommentsAdd REST API to Take Ownership of Fabric Pipelines
When using service account to automatically deploy Fabric pipelines from Dev workspace to upper environments, the owner of pipelines in target envionment remain unchanged. In some situations, per...VickyPeng2 days agoRegular VisitorNew367Views5likes2CommentsUpdate the 'Users can set up email subscriptions' in Fabric Admin Portal to specific groups
I want to be able to allow a specific group of users to set up email subscriptions. In my admin portal view I only get the following Can this be updated to allow specific user groups? ...Chart682 days agoNew MemberNew138Views1like1Comment