Renovate creates duplicate MR right after original MR has been merged

When I merge an MR created by renovate bot, quite often renovate immediately creates a duplicate MR suggesting the same change.

Example:

• original: gitlab-org/gitlab-vscode-extension!470 (merged)
• duplicate: gitlab-org/gitlab-vscode-extension!473 (closed) (created 7 mins after original has been merged)

This happens in roughly a third of the cases when I merge a renovate MR.

I think this is caused by a slow mirroring of the renovate fork (https://gitlab.com/gitlab-renovate-forks/gitlab-vscode-extension) but I don't have access to the fork project settings to validate this assumption.