Open mjgabriel opened 4 years ago
I faced same issue as @mjgabriel.
Removing all collections/containers from local cosmos emulator DB resolved the issue.
I have same issue now, I cannot delete the collection as I get same error "Collection is not yet available for read"
Describe the bug Exception information from code, please note the emulator was already up and running before hitting it via service code.
Error message reported by the emulator provided data explorer
To Reproduce Start emulator. Create container. You can access the container via code, the data explorer available at https://localhost:8081/_explorer/index.html You can access it via Storage Explorer. Shutdown emulator. Restart emulator. You can no longer access the container via code or the data explorer provided by the emulator.
Expected behavior I would expect the containers created to remain accessible between emulator usage sessions.
Actual behavior Can't access containers created during previous emulator session/usage.
Environment summary
SDK Version: Microsoft.Azure.DocumentDM 2.5.1 OS Version (e.g. Windows, Linux, MacOSX): Windows 10 Pro Build 19041
Additional context Please note, even using the data explorer provided via the emulator I can't access the container previously created.