Hi Derek,
The commit of the object (the transaction) is actually processed after completing of the microflow, so if you use a rollback before this moment, the object will be reset to the state of the last commit: In this case with the old status.
My advice would be not to rollback the object, or to use an endTransaction Java action (which basically executes the commit to the database immediately). You can find this action in the Community Commons.
Shouldn't this resolve your problem then you could also post a screenshot of your Microflow so we can look further into this issue.
Jordy
And do not forget the community commons commitInSeparateDatabaseTransaction. When you use this Java action the commit will be seen by other microflows etc because it will commit the object in it's own transaction.
Regards,
Ronald