This might be because the roast-time folder contains your user-specific configuration record. This record is used to determine which version of RT services you should be using. If it’s deleted, RT will default to the version that comes installed with it (which I think is 1.42.2.
I’d recommend not deleting or changing files in roast-time folders as this isn’t meant to be changed manually and can lead to unexpected changes in RT. If deleted, RT will revert to its default settings and take a few minutes to update to the correct service versions.
Just tacking on to what Derrick mentioned - the update process is tightly coupled to being online (the beta and early tester opt in checks, etc) and there is the possibility of a bug in here that may be causing your issue if you are primarily offline (maybe its trying to revert to the packaged version like Derrick mentioned). I will create a ticket to test.
After I sign in an update, I don’t delete the roast time folders. Otherwise I’d have to sign in again.
However, when I go into settings, it does seem to suggest that I may be on proxy service 1.42.2, even though I have already updated.
It also shows the RT4 version as v4.6.26, if that means anything to this issue.
Seems if I get the edit on the roast shortly after an update, I can get the edit to stick, but later on it starts reverting titles to whatever they were during the roast.
Tried out the official release. Everything felt normal and update was smooth.
Seems to be working, but will have to give it 48hrs at least to know for sure, but this has been the first time an update felt normal since I moved to RT4.