[INACTIVE] Assets Upload duplicate media

I have…

  • [ ] Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [x] Bug report
  • [ ] Performance issue
  • [ ] Documentation issue or request

Current behavior

Whenever we try to replace an asset via API, the operation does go well , but it always create a duplicate in filesystem. This way it’s confusing because on the platform we see the right number of assets but in filesystem and in the database the count is way larger. all this media goes into the backup archive and for this reason is impossibile for us to successfully back up and restore the database via the normal platform procedure.

Expected behavior

Override Media instead of create any duplicate or asset

Minimal reproduction of the problem

Upload image via API


  • [ ] Self hosted with docker
  • [x] Self hosted with IIS
  • [ ] Self hosted with other version
  • [ ] Cloud version

Version: [3.5]


  • [x] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [x] Firefox
  • [x] Safari (desktop)
  • [ ] Safari (iOS)
  • [x] IE
  • [x] Edge


This is intended. Everything in Squidex has a history, also the assets.

ok , but why the restore procedure fail with many assets? if it’s an intended feature the procedure must handle by design al very large number of assets. Unfortunatelly it fails with 8k assets

I don’t know, can you share logs or the exception details?