It seems that it's a bug that may happen on very rare cases. The graph is not refreshed properly. This bug is opened on the R&D side. It will probably be fixed in the next NeoLoad version but not sure if it will be the case of the 5.0.x versions.
No similar question