Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
Hi,
since a few days all pipeline acitivities with fabric warehouse connecions (stored procedure, lookup) remain in queued status for a long time (> 90s) before they become active. The "real" execution of the stored procedure tooks only 3 seconds.
Does anyone have similar problems or know a solution?
Thanks!
Solved! Go to Solution.
Hi @cw88,
I recommend raising a support ticket so that an engineer can investigate the pipeline orchestration logs and check for any internal delays affecting your runs.
Below is the link to raise the support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
Hi @cw88,
Could you please confirm if the issue was resolved after raising a support case? If so, we’d appreciate it if you could share the solution to help others in the community.
As we haven’t heard back, we’re closing this thread. For any further issues, please start a new thread in the Microsoft Fabric Community Forum — we’ll be happy to assist.
Thank you for being part of the Microsoft Fabric Community.
Hi @cw88,
Thank you for reaching out to the Microsoft Fabric Forum Community.
The issue you are encountering with Pipelines queue activities may be due to a bottleneck in the Fabric pipeline service or because other activities or dataflows are simultaneously consuming capacity.
Avoid running multiple heavy activities simultaneously and consider scheduling pipelines during off-peak hours if on shared capacity.
Check the Fabric Capacity Metrics App.
And look for:
Thank you.
Hello @v-saisrao-msft
unfortunately this is not the case. The test runs in isolation on a trail capacity, no other activities run in parallel or with other jobs.
What do you mean with "bottleneck in the Fabric pipeline service"?
Hi @cw88,
I recommend raising a support ticket so that an engineer can investigate the pipeline orchestration logs and check for any internal delays affecting your runs.
Below is the link to raise the support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.