Yep., from my experience though it only seems to happen when you have a customised screen, Epicor does not touch the customization and it is holding the original value, AFAIK (or remember at least) base forms don’t have this issue, could be wrong though but everywhere I have personally seen it, I had a custom layer at play on the screen that was making the call.
And it seems like in 2025.1 testing I had a slightly different but somewhat related problem, we skipped 25.1 so I did not do much more on it: