Hello @Vimlesh Rivonkar
There could be various reasons why your pipeline is stuck in the queued status. It could be due to hitting concurrency limits, service outages, network failures, and so on.
Let's try to troubleshoot the issue step by step. First, check if your pipeline has a concurrency policy assigned to it. If it does, go to the Monitoring view, and make sure there's nothing in the past 45 days that's in progress.
If there is something in progress, you can cancel it, and the new pipeline run should start. If there are no old pipeline runs in progress, it is possible that your run was impacted by a transient network issue, credential failures, services outages, etc.
If this happens, Azure Data Factory has an internal recovery process that monitors all the runs and starts them when it notices something went wrong.
You can rerun pipelines and activities as described here: https://docs.microsoft.com/en-us/azure/data-factory/monitor-visually#rerun-pipelines-and-activities.
You can rerun activities if you had canceled activity or had a failure as per Rerun from activity failures. This process happens every one hour, so if your run is stuck for more than an hour, create a support case. If the issue persists, please provide me with more information like the error message or any other details that you see in the pipeline run details. It will help me to provide you with a more specific solution. Let me know if this helps.
I hope that this response has addressed your query and helped you overcome your challenges. If so, please mark this response as Answered. This will not only acknowledge our efforts, but also assist other community members who may be looking for similar solutions.