MR pipeline gets triggered before the regular pipeline resulting the latter to be shown in MR interface

Summary

Usually, the MR pipeline gets triggered after the regular pipeline and then it shows up in the MR interface. But sometimes a regular pipeline follows the MR pipeline. Hence the result of a regular pipeline is shown.

This prevents us from doing MR specific things like manual triggering jobs from MR interface.

Steps to reproduce

We have a job that should be a part of MR pipeline and a regular pipeline. The relevant part of the definition is the following

only:
    refs:
      - merge_requests
      - branches

When a commit is landed on a branch with MR this configuration triggers two pipelines. And the order seems to be vague.

What is the current bug behavior?

The regular pipeline runs after the MR pipeline, hence the result of the regular pipeline is shown in MR.

What is the expected correct behavior?

If the MR pipeline gets triggered the result of this pipeline should be shown in MR always.

Relevant logs and/or screenshots