Note the following limitation:
All Fluent as a Server commands and most aaS commands cannot be executed until Fluent is idle or at a stable point. For example, Fluent is not stable while solving for an iteration, but at the end of the iteration there is a stable point. This means that there may be a lag between when you enter a command and when you receive a response.
The minimum
lag during a solve operation is one iteration, though you may choose
settings that have the effect of increasing it. See Fluent as a Server Commands (fluent.) and Collaborative Commands for strategies for minimizing
this lag for Fluent as a Server commands and aaS commands, respectively. For
a list of aaS commands that can always provide an instant response
(that is, without the possibility of a lag), see Instant Commands.