Thanks for the response. After submitting this post, I realized that this issue is due to the assignment being routed to the current user. We want to do this because we want the current user to complete the duplicate-resolution step. But if the user cancels or abandons the assignment, we want the case to remain in the work queue from which it was originally retrieved, instead of being routed to the user's worklist.

My concern is that this requirement deviates significantly from the Pega's design for handling assignments, and that implementation will be unreasonable or overly complicated. But if we are to attempt this implementation, my thought is that we will need to route the assignment to the work queue, and then manually open that assignment for the current user once the flow reaches that step.

Any advice about how to accomplish this?