Issue

When using the $currentUser variable in a microflow, the data of the current user is outdated. A change that was made in a previous action is not updated. This also applies to a specialized user entity (like Administration.Account) which was cast from the $currentUser. 

Environment

Studio Pro 9.8.0 and above. 

Cause

Since Mendix Studio Pro 9.8.0, the current user will no longer always be retrieved from the database before the microflow is executed, which means the current user in a microflow might not be completely up-to-date. The current user is now retrieved from the current session, which means that the data of the current user may lag behind 10 seconds (sessions are cached for 10 seconds). 

Solution/Workaround

Retrieve the current user (with a microflow) from the database using the $currentUser token.

Additional information

Not Applicable