In a multitenant environment a certain background job calls community commons executeAsUser because the microflows have 'Apply entity access' enabled and this must absolutely be executed as a user.
The microflows runs for more than 15 minutes and the Log is flooded with messages that Mendix can not delete the session. If we change the executionType of the microflow to SCHEDULED_EVENT the messages disappear but the cache is corrupted with orphan objects with owner UNKNOWN.
We have increased the sessionTimeout but that has unwanted side-effects
Is a solution available for this?
EDIT1:
After building a test project that successfully shows this behavior we found that setting the context executionType to CUSTOM will solve this.