Forum Discussion
Data pipeline is remaning into InProgress state
Hello ankitmori91,
The F4 capacity alone does not tell us why the pipeline is taking 15–25 minutes.First check the pipeline run and open the Notebook activity details. Fabric shows the activity duration and performance details in the pipeline run. Check those first to see where the time is being spent.
Try running the Notebook on its own and see how long it takes compared with the pipeline run.
If the Notebook itself takes 15–25 minutes, investigate the Notebook execution. If it completes much faster but the pipeline remains InProgress, the pipeline activity details should help narrow down the cause.
Microsoft Learn: Monitor pipeline runs in Fabric Data Factory
Super UserHello ankitmori91,
The F4 capacity alone does not tell us why the pipeline is taking 15–25 minutes.
First check the pipeline run and open the Notebook activity details. Fabric shows the activity duration and performance details in the pipeline run. Check those first to see where the time is being spent.
Try running the Notebook on its own and see how long it takes compared with the pipeline run.
If the Notebook itself takes 15–25 minutes, investigate the Notebook execution. If it completes much faster but the pipeline remains InProgress, the pipeline activity details should help narrow down the cause.
Microsoft Learn: Monitor pipeline runs in Fabric Data Factory