Forum Discussion
Query Regarding Data Pipeline Executions: Prolonged Queued Status and Connection Failures During Edi
Dear Microsoft Fabric Community,
I am currently operating a suite of four Data Pipelines within my Fabric environment, all of which are scheduled to execute successfully throughout the day. Specifically, one of these pipelines runs with a daily frequency of four times.
I am seeking feedback from the community regarding two recurring anomalies I have recently observed:
1. Prolonged Inactivity in "Queued" Status
Occasionally, one of the activities within the pipeline remains in the "Queued" state for an unusually long period, ultimately leading to a Time Out.
Question: Has anyone else experienced this intermittent behavior where activities get stuck in the scheduler despite apparent resource availability, resulting in a Time Out? I would appreciate any insight into potential causes, such as capacity resource contention (SKU) or integration runtime configurations.
2. Connection Failures When Editing Pipelines
I have noticed that when attempting to edit the configuration of my existing pipelines, the connections (Linked Services) that were previously validated and functional appear as "failed" or invalid within the editing interface.
Any guidance or shared experience on these points would be highly valuable for the operational stability of my environment.
Thank you very much in advance for your cooperation!
Hi Glopez9829,
Thanks for reaching MS Fabric community support.
-
Activities stuck in “Queued” – Some activities remain queued for a long time and eventually time out, likely due to capacity contention or concurrency limits.
-
Connections showing as failed when editing – Linked Services appear invalid in the editor, likely due to token refresh or temporary UI validation issues, even though they run successfully.
Both issues seem to occur during heavy load or service synchronization. Monitoring capacity and validating authentication tokens are key. If this happens frequently, consider increasing capacity or separating production pipelines into their own capacity.
Thanks,
prashanth
-
3 Replies
Hi Glopez9829,
Thanks for reaching MS Fabric community support.
-
Activities stuck in “Queued” – Some activities remain queued for a long time and eventually time out, likely due to capacity contention or concurrency limits.
-
Connections showing as failed when editing – Linked Services appear invalid in the editor, likely due to token refresh or temporary UI validation issues, even though they run successfully.
Both issues seem to occur during heavy load or service synchronization. Monitoring capacity and validating authentication tokens are key. If this happens frequently, consider increasing capacity or separating production pipelines into their own capacity.
Thanks,
prashanth
-
We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community supportHi Glopez9829,
We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support