late or no completion of ISAC scenario after end of load profile
A scenario may not complete while the execution time specified by the load profile has elapsed, even with the "force stop" flag enabled. Of course, this can occur when the number of virtual users has been changed manually during the test execution (change parameters command), which is completely normal, since this operation cancels the load profile.
But this may also occur when scenarios contain a never-ending loop (e.g. while true...) with no timer call (aka think time). In case there is no loop but just a sequence of actions without timer, the "force stop" flag is still ignored, and the actual completion will wait for all virtual users to execute the very last instruction of their behavior (exactly as if the "force stop" flag had not been set). This situation is actually a bug.
A very simple workaround is to include a timer call, even with a very short think time, in the behavior section where the virtual users execution might be dropped. This will make the "force stop" flag to be taken into account.