Ok, I have good news and bad news on this one for you @philip
The good news is it’s a very fresh bug, not many cases of it, but the developer has seen it and feels confident its been fixed.
The bad news is because its so new the fix did not make it into the 3.2.1 firmware update due out later today. (Mostly an Ignition version update, but they did address ‘your’ bug in it: RIO Save to flash / custom data access area not persisting - #2 by Beno with KB89662 showing it was fixed in 3.2.0, but I see it fix in the readme for 3.2.1 - sooo, uh…)
If your strategy can be tickled to cause the bug at will it would be helpful for our guys to use it in testing.
If so, please reach out to our support team.