@ohoral first reported this in Slack for https://gitlab.com/gitlab-org/gitlab/-/merge_requests/54138 and I experienced the same in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/55671  @fabiopitino mentioned that the `actual_head_pipeline` being checked by the MR widget is referring to the last fork pipeline even though newer pipelines for merged results have been run. I worked around this by retrying failed jobs in the last fork pipeline so that it goes back into the running state and I can set MWPS.