Struggling with running DQ Scans (Long queuing and Retry Count Error Issues)

Hi everyone,

I have been exploring Microsoft Purview Data Quality quite extensively. At this point, I have configured more than 4,000 data quality rules across more than 10 Microsoft Fabric capacities, each with a minimum capacity of F16. Fabric is the source for all assets registered in Purview.

I have identified several issues with the product, but the two that are currently impacting me the most are the following:

1. DQ scans failing with a generic error“Max Retry Count Reached. Ending Workflow. Current Task HandleError”The challenge is that the error message does not identify which rule is causing the failure. As a result, I have to troubleshoot manually by disabling groups of rules, rerunning the scans, and repeating the process until I find the problematic rule. This trial-and-error approach is very time-consuming, especially at this scale.
2. This seems to be caused by issues in some of the DQ rules, even though all rules are marked as “Good to go” in Purview.
3. When running Data Quality scans, I often receive the following error:
4. DQ scans remain queued for a long timeI am not sure why this happens or what resource, orchestration, or scheduling constraint is causing the delay.
5. Whenever I run these DQ scans, they remain in a Queued state for at least 10 minutes, even when there is nothing running on the Fabric capacities.

Has anyone experienced similar behavior with Purview Data Quality at this scale?

Specifically, I would appreciate any guidance on:

• How to identify which DQ rule is causing a scan failure
• Why scans remain queued even when Fabric capacity appears to be idle
• Whether there are known limitations or best practices for running thousands of DQ rules in Purview

Thank you.