When the "Refresh in client" action is used within a microflow executed by a task queue in Mendix, no action is taken to refresh any user's interface. This is because task queues operate asynchronously in the background on the server and are not connected to any specific user's session or client.

The primary function of the "Refresh in client" setting, which is typically used in Commit or Change object activities, is to instruct the Mendix client—the user's web browser or native mobile application—to update its view of the data. This action is contingent on the existence of a client session that initiated the process.

However, microflows running in a task queue are initiated by the server itself, independent of any user interaction. As a result, there is no client context to which a refresh command can be sent. The Mendix runtime environment simply disregards the "Refresh in client" instruction in this scenario.