This is an issue with how powershell sometimes doesn't always honor the -Wait flag. for example, if the editor was already open before the user requests to open his/her encrypted file, it's seen to not respect that (e.g. with .txt files and Visual Studio Code)
Inside CipherDocs.ps1 at Line 68 we do something like
Start-Process $tempClearFilePath -Wait # <== problem-o !
to launch the file and wait before CipherDoc reviews file state for re-encryption.
Since this is flaky, we need a better mechanism for that. Maybe monitor the file for changes (file system monitor?) as long as it's got open handles? Or ... ?