Could be, thought the same
If the calculation for FLEX perhaps hit the limit of Vmcg in an iterative manner, could it be the SW defaulted into TOGA results (similar to the fixed printed scenario above) instead of re-doing the FLEX values properly?
. I.e the SW is not calculating the perf. data, but rather looking them up instead. If it's a 3rd party provider not likely they have much other choice.