File Sync Conflict occurs without clear Notification

[db-ot]

Steps to Reproduce

• Create a .txt file.
• Open the file in the web application and in a local application at the same time.
• Make different changes in both versions.
• Save both versions (first the local file, then the web version).
• Close both applications.
• Open the sync process.
• A small temporary message appears and disappears after a few seconds.
• A conflict file is created without any clear explanation.

Expected Behavior

• The user should be clearly informed that the file is open and modified in multiple locations.
• When a conflict occurs, the warning or error message should remain visible longer or appear as a prominent notification.
• The conflict file should be clearly explained, or the user should be explicitly notified that a duplicate/conflict file has been created.

Actual Behavior

• No clear notification is shown by the background sync service.
• Only a short-lived message appears in the sync service UI and then disappears.
• There is no notification that the file was opened or modified in multiple locations.
• A conflict file is created with the title “conflicted copy ” without any further explanation.

Screenshots / video

• https://opencloud.stiftung-mercator.ch/s/LbiLUoYNtdQdMvf

• temp conflict message in sync browser ( 2 seconds )

• conflict file