We recently migrated an existing team project to a new Azure DevOps Server and find that with our release pipelines, we are seeing that they don't trigger upon a build completion like they did prior to the migration to the new server. In some cases, we see the releases trigger many hours later (like 14-16 hours later) We're using a continuous deployment trigger subscribed to a build pipeline. We're using classic build and release pipelines. Need some help troubleshooting this. See the images I've attached below. The build is attached to a github enterprise server repo. When I manually trigger the release, it grabs the artifact from the build as expected.
Here is the release pipelines artifact subscription to the build pipeline
Here is the continuous deployment trigger configuration on the release
This shows how the release eventually triggered many hours after the build completed
I expect the release to be triggered directly upon completion of the build to which it is subscripted in the Continuous Deployment Trigger.