dosya.dev Help

Resolve a copied-file name conflict

Resolve a copied-file name conflict. Follow a controlled workflow, verify the result, and avoid changing the wrong workspace or item.

Last reviewed

Resolve a copied-file name conflict is safest when you verify the account, workspace and target before committing the action. This guide uses a small controlled example so you can confirm each state.

Before you start

  • Open Files → Copy in the current released Dosya client.
  • Confirm the active account and workspace, then identify a test file whose name already exists at the destination.
  • Use non-confidential test data and record the current state before changing it.
  • Keep passwords, API keys, recovery keys and private links out of screenshots and support messages.

Steps: resolve a copied-file name conflict

  1. Open Files → Copy and confirm the active workspace.
  2. Select a test file whose name already exists at the destination and check its name or identifying details.
  3. Review the conflict choice and keep both items with clear names.
  4. Read the confirmation, warning or progress state before leaving the screen.
  5. Verify that no existing destination file was silently replaced.
  6. Refresh or reopen the view once to confirm the result persisted.
Dosya file preview and detail surface used to confirm the selected file before an action.
Confirm the selected file and workspace before changing or copying it. Open full-size screenshot.

Expected result

The workflow completes for the controlled test and no existing destination file was silently replaced. The result remains visible after a refresh or reconnect.

Limits and important details

  • Available controls depend on the current client version, plan, role and workspace policy.
  • Actions may be blocked by folder locks, hidden-item rules, storage limits or a restricted credential.
  • For destructive or access-changing actions, test with disposable data before applying the workflow to important files.

Troubleshooting

The expected control is missing. Return to Files → Copy, confirm the active workspace and check that your role permits the action.

The operation is rejected. Read the exact message and check access, locks, quota, network state and client version before retrying.

The result is unclear. Repeat with one small test item, then contact support with the time, client version and a nonsecret error message.

Continue with another task

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

About views and your privacy

Views count page openings, not reading or task completion.

View measurement is off by default. If you enable it, a separate 30-minute cookie prevents repeat openings from increasing the count. We do not use fingerprinting or connect this session to uploads or shares.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.