I’ve also experienced this bug, and have reported it. I have a sort-of-workaround below that will at least allow the loading of the rest of the non-corrupt conversations in a project.
I’ve noticed this:
If I load that project in the web app, it will display on the conversations up to (approximately) the corrupt conversation. It never finishes loading, so conversations older than that corrupt one are not visible.
Today I checked for updates on the mac app, and lo and behold, there was an update. After installing the update, I can load that project in the app, and at least all the conversations are visible and viewable, except the corrupt one, which won’t load. There’s also a message at the bottom “Unable to load, retry?”.
WORKAROUND:
You must use the most up-to-date desktop app for this workaround. This won’t work on the web. I haven’t tested this on Windows, only the Mac client, but it may still work on Windows.
- Create a new project that mirrors the project with the corrupt conversation: Prompt and Files
- Move all conversations one-by-one, except the corrupt one(s), to this new project. The corrupt conversation(s) will be displayed in the list, but will fail to move.
- Rename the corrupt project something else - it will only have the corrupt conversation(s) left in it.