[Bug?] row_already_exists (409) after manual deletion, stale unique index?

Hi, I'm experiencing a confusing issue with Appwrite Cloud

Setup: A tournaments table with a composite UNIQUE index on (tournament_name, date).

Steps to reproduce:

Delete a row manually via the Console Verify deletion: getRow(deletedId) → 404 ✅ listRows by tournament_name + date → 0 results ✅

Try to createRow with the same tournament_name + date values → 409 row_already_exists: "Row with the requested ID <OLD_ID> already exists."

The error references the old deleted row's ID, which proves the unique index still holds a stale reference to it.

Is there a known TTL or async cleanup delay on unique index entries after a row is deleted via the Console? Is this a known limitation? Is the behavior different when deleting via SDK vs Console? Is there a way to force-clear a stale index entry (other than trying to deleteRow the ghost ID and hoping it flushes the index)?

I've seen nothing about it in the docs

Thanks