Previously you could delete records and import a new record with the same name via CSV and it would be fine.
Now it won’t do it as it says there is a slug already in the database. But why does it keep the old slug if it’s deleting it?
My use case was previously have a ton of CMS items that would get replaced daily by deleting the old records and importing the updated records via CSV. I am now having to do this manually and it is almost impossible to maintain.
You’re doing CSV imports?
I’d probably automate that via the API if possible, for your scenario.
My understanding is that since the item-level-publishing feature was released mid Dec, the “reserved slug” situation can occur in certain scenarios until you republish.
So since you’re doing CSV imports, you’d delete what you want, then republish the site, then CSV import.
Note you can also update records with CSV, it may not be necessary to delete at all?