Don't know if this is what happened to you, but what still confuses me momentarily whenever it happens to me is that a save does nothing if you haven't selected a directory to save the file in AND you are not notified what the problem is, leading to the repeated save attempts you noted. I've also seen this with software other than SAS Studio - wish UI/UX folks would address this, because it can drive one crazy! 😀
The other gotcha here is that SAS Studio does a good job of making unsaved changes available when you open your next session, but ONLY if you've done an initial save. Again, this can happen with other software, but if SAS is looking for enhancement ideas, I like the approach that software like Jupyter, VS Code, and Snowflake have adopted, which is to make unsaved code available across sessions in a default name (e.g., as untitled-1.pynb), although I have to confess I didn't like this practice at first! 🙂
