One possible cause of the issue could be hitting concurrency limits. To check this, verify that there are no ongoing old pipeline runs if your pipeline has a concurrency policy. You can do this by going to the ADF authoring canvas, selecting your pipeline, and checking if a concurrency property is assigned. If it is, switch to the Monitoring view and ensure there are no runs in progress from the past 45 days. If there are, cancel them to allow the new pipeline run to start.
Another potential issue could be monitoring limits. Additionally, your run might be affected by transient network issues, credential failures, service outages, etc. Azure Data Factory has an internal recovery process that monitors runs and restarts them if it detects a problem. This process runs every hour. If your run has been stuck for more than an hour, create a support case.
For more detailed information, refer to the Azure Data Factory documentation on handling pipeline statuses that are queued or stuck for a long time.
https://learn.microsoft.com/en-us/azure/data-factory/monitor-visually#rerun-pipelines-and-activities