Sorry to hear this - nothing is registering as being overly delayed right now so we'll have a team member investigate.
As a note, merge jobs can be slow if the groups are huge, but generally is managed as an offline task. They do queue, so if you have one really massive merge job, and a bunch of small ones, it may look slower than it is.
Changing the status to resolved though shouldn't be slow since that's just updating a status field on a database row, so we'll look into that too.
Usually in these situations it can just be a queue of merge jobs, and there's no action to be taken (other than continuing to think of ways to make it faster for everyone), but I'll update here on if something significant is found.