The user encountered an issue where duplicate cases could not be merged and received the error:
Couldn't merge records
We can't merge these cases. One or More of the cases are in an Omni-Channel queue.
This behavior was observed when using the Status-Based Capacity Omni-Channel Model.
To resolve the "Couldn't merge records" error in Omni-Channel with Status-Based Capacity Model, ensure only one case is in an In-Progress or Paused status before merging, and designate that case as the principal record.
To confirm if you are using Status-Based Capacity Model, navigate to Setup > Omni-Channel Settings and verify if "Enable Status-Based Capacity Mode" is enabled.
If you are not using Status-Based Capacity Model, cases need to be assigned to a User in order to be merged.
To identify which statuses correspond to In-Progress, Paused, and Completed values, navigate to Setup > Service Channels and open the channel where the Salesforce Object is Case.
005237035

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.