Apologies – I’m unfortunately unable to provide screenshots of our domain model or microflow. The microflow is huge and would better be called a “macroflow” at this point.
We ended up figuring out the issue was indeed caused by Rollback behavior specifically where the reference selector field on the page is a dropdown. Even though the value wasn’t being changed in the microflow at all, the rollback behavior starting a new transaction would for some reason default the dropdown’s value to the first in the list (alphabetically) instead of what it already was. We weren’t picked up on this because that field has conditional editability set to never, so we didn’t think users would ever been able to change it.
So far, replacing the dropdown with a nested dataview (since it was only for viewing) has been working. Or at least we haven’t seen the issue happen again since.