This has been implemented like that for a while, seems like it did not meet the threshold in your case.
There can be multiple reasons for that, for example just a very slight difference between the physical and digital environment can have significant impacts on singularities, i.e. the difference between high and infinite/too high speed.
Or as we simplify the robot models per reach, a higher-payload robot may not reach the speed of a lower payload robot.
However, as the speed calculations are kind of rough anyway as the acceleration ramps of the motors etc. are not known, it's always an approximation.
So in summary, the easiest approach may be to allow the user to change the threshold when the notification triggers. Can you send me your file via mail? I'm curious how much change it would need.