[Bug]: Select All Existing File for conflict does not work

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

Currently, when moving files or folders from one location to another, if a naming conflict is detected—such as an existing file or folder with the same name—the 'Apply to all' option doesn't work as expected. Each conflicting item must still be handled individually.

Steps to reproduce

1. Move files from one directory to another. Ensure the destination already contains some duplicate files or folders.
2. When prompted, choose the option to "Keep duplicates" and select “Apply to all” for existing files.
3. Click “Continue” to proceed with the operation.
4. Instead of applying the choice consistently, the system still prompts you to resolve each conflict individually—forcing you to confirm each duplicate one by one.

Expected behavior

Once a user selects all existing files it should bypass all files or folder and not ask the user

Nextcloud Server version

31.0.7

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.4

Web server

Apache (supported)

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

Updated from a MINOR version (ex. 32.0.1 to 32.0.2)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response

Start by reproducing the file move with duplicate files or folders on Nextcloud Server 31.0.7, using “Keep duplicates” and “Apply to all.” Trace the conflict-resolution flow from the prompt and verify that one selection handles every conflict without further prompts; no source files or tests are identified in the issue.