CLI returns an error (validateVaultItem) non-unique name

Update:

Debug logging

9:40AM | DEBUG | Session delegation enabled
9:40AM | DEBUG | NM request: NmRequestAccounts
9:40AM | DEBUG | NM response: Success
9:40AM | DEBUG | NM request: NmRequestAccounts
9:40AM | DEBUG | NM response: Success
9:40AM | DEBUG | account not signed in, filter= latest_signin_user=
9:40AM | DEBUG | NM request: NmRequestAccounts
9:40AM | DEBUG | NM response: Success
9:40AM | DEBUG | NM request: NmRequestAuthorization
9:40AM | DEBUG | NM response: Success
9:40AM | DEBUG | NM request: NmRequestAccounts
9:40AM | DEBUG | NM response: Success
9:40AM | DEBUG | NM request: NmRequestDelegatedSession
9:40AM | DEBUG | NM response: Success
9:40AM | DEBUG | NM request: NmRequestAccounts
9:40AM | DEBUG | NM response: Success
9:40AM | DEBUG | InitDefaultCache: successfully initialized cache
9:40AM | DEBUG | EncryptedKeysets: Cache hit on keyset
9:40AM | DEBUG | AllVaults: cached vault xwjgl2uxfh2h5d22d6qdkzvrwi is outdated - invalidating
9:40AM | DEBUG | SetVault: successfully cached vault xwjgl2uxfh2h5d22d6qdkzvrwi
9:40AM | DEBUG | SetVault: successfully cached vault 7vu76sel67uvzs7wfcygkl63yu
9:40AM | DEBUG | SetVault: successfully cached vault pv4rppbqr2qr3ofj7ki3xuaiia
9:40AM | DEBUG | SetAllVaults: successfully cached all vaults
9:40AM | DEBUG | VaultItems: cached vault items of vault xwjgl2uxfh2h5d22d6qdkzvrwi is outdated - invalidating
9:40AM | DEBUG | SetVaultItems: successfully cached vault items of vault xwjgl2uxfh2h5d22d6qdkzvrwi
9:40AM | DEBUG | VaultItems: cache hit on vault items of vault xwjgl2uxfh2h5d22d6qdkzvrwi
9:40AM | DEBUG | Item: VaultItems cache hit for vault xwjgl2uxfh2h5d22d6qdkzvrwi - validating staleness using item version
9:40AM | DEBUG | Item: cache hit on item 46a77tbfxpghwag4xtgowa5ftm of vault xwjgl2uxfh2h5d22d6qdkzvrwi
9:40AM | DEBUG | Vault: cache hit on vault xwjgl2uxfh2h5d22d6qdkzvrwi
[ERROR] 2024/02/12 09:40:00 validateVaultItem failed to Validate: Couldn't validate the item: "[ItemValidator] has found 1 errors, 0 warnings: \nErrors:{1. details.sections[1] has non-unique name}"!

Where id xwjgl2uxfh2h5d22d6qdkzvrwi = Private vault id
Where id 46a77tbfxpghwag4xtgowa5ftm = Ssh key id 'name'-'date now yyyyMMddmm'

Doublechecked with "op item list --vault Private" if there are duplicate names and there is none.

Both command:
"op item delete 46a77tbfxpghwag4xtgowa5ftm --vault Private" as
"op item delete 'name'-'date now yyyyMMddmm' --vault Private"
return the same message.

Cleared up "recently deteled items" and "archive"

I am also encountering this issue and it is blocking my automation scripts.

I am in contact with support however there is some radio silence at the moment.

My gut feeling tells me that it has something to do with the local cache. But, I do not have a good feeling poking too much myself with removing caches and such.

When I have an update I will update it here as well.

This is happening with move operations on SSH Key items as well.

Hey folks, my apologies for the troubles here and the delay in getting this sorted! It looks like this is a bug specifically affecting management of SSH key items through the CLI. The Development team is aware of this issue and is working on a fix. Keep an eye out on the 1Password CLI Releases page for updates.