Forum Discussion

Glopez9829's avatar
Glopez9829
New Member
9 months ago
Solved

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. Speci...
pipelines
  • v-prasare's avatar
    v-prasare
    9 months ago

    Hi Glopez9829,

    Thanks for reaching MS Fabric community support.

     

    1. Activities stuck in “Queued” – Some activities remain queued for a long time and eventually time out, likely due to capacity contention or concurrency limits.

    2. 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

v-prasare's avatar
v-prasare
Community Support
9 months ago

Hi Glopez9829,

Thanks for reaching MS Fabric community support.

 

  1. Activities stuck in “Queued” – Some activities remain queued for a long time and eventually time out, likely due to capacity contention or concurrency limits.

  2. 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