Older pipelines with Pipeline status not matching job status

Problem

An incident caused us to read from the replicas in PipelineProcessWorker when it's critical to have fresh data. 2024-10-08: Pipelines not completing and Stuck ... (gitlab-com/gl-infra/production#18676 - closed)

That incident left behind some pipelines which are still in the running state but where all the jobs are finished. gitlab-com/gl-infra/production#18676 (comment 2194929360)

This is appears to be mostly a UI inconsistency at this point because these 4 week old pipelines are likely no longer relevant for mergability status checks or notifications. It might not be worth fixing this even, especially if customers are not complaining.

Solution

It would be safe to run PipelineProcessWorker on any pipelines that are in this state since the builds are all finished it won't affect minute consumption which is accumulated per build when a build finishes.