Occasionally when moving or reorganizing content in the journals tab (folders, handouts, characters, etc), the target object is cloned. I hesitate to say duplicated, and I don't think cloned is exactly right either; after the cloning occurs, both instances act identically. If I, for example, update the text in a cloned handout, the other cloned instance is updated too. I try to archive or delete the duplicate, guess what - both are gone. For all intents-and-purposes, it would seem it's not actually two objects, but two journal entries for the same object. From what software experience I have, it's very reminiscent of a SQL indexing error where two unique IDs are attached to the same source object in the relevant table. Both IDs access and update the same object because, as far as they're concerned, they are the same object. It doesn't happen often but it does happen often enough to warrant a problem. The only fixes for the issue that I've been able to find is to delete and recreate the duplicated content from scratch, or to rollback the game. The latter option is only for pro users and is quite frankly an excessive solution, and the first option can be cumbersome if it's more than a few handouts or any special formatting has been done. I'm not sure how difficult this may be, but assuming it is an indexing thing like I suspect, something that periodically scans (or can be triggered with a button click) for and cleans up duplicate journal entries would be super handy.