Trying to restore files via webDAV has apparently caused DB/filesystem conflicts

Per the documentation, I am trying to restore files by ID, using the TrashBin API. The format I am using:

curl "http://owncloud.server/remote.php/dav/trash-bin/user1/1234567/" \
  -H 'Overwrite: F' \
  -H 'Destination: http://owncloud.server/remote.php/dav/files/user1/Graphics/BMP/file001.bmp' \
  -X MOVE \
  --user "user1:pass"

When attempting this, I receive an error that the "destination node already exists". However, the file is still in the trash directory and it is not in the Destination directory. I don't know where to find the node in the database but it does not exist anywhere on the filesystem, outside of the trash.

Expected behaviour

The file is restored.

Actual behaviour

I receive an error:
The destination node already exists

Steps to reproduce

This issue appeared when trying to restore 200,000 files, using the TrashBin DAV API.
Per the documentation, calls used the file ID and a target path.
Around 180,000 succeeded and the rest seem to have this issue.

Server configuration

Operating system: Linux
Web server: Apache
Database: MaraiDB
PHP version: 7.3
ownCloud version: 10.5.0

Client configuration

N/A

Logs

N/A

Start at the TrashBin DAV API handling of MOVE requests with an ID and destination path, then reproduce the conflict using the documented curl request. Check how the destination node is detected when the file remains in trash. Done means the file is restored to the target path without a false existing-node error.