Stuck in cycle of save VI dialogs

[Worle]

Has anyone else noticed that in LabVIEW 2023 you can stuck in a cycle of Save Dialogs when trying to save a VI (The save dialog just keeps coming back up asking me if I want to save the VI). I have specifically noticed it when trying to save an override VI in a child class.

I haven't managed to work out a pattern to it yet nor have I managed to replicate it on a simple test project. Closing LabVIEW and restarting seems to solve the problem.

I have never had this on older versions of LabVIEW but have only started using OOP heavily in the last couple of years so it may be an issue linked to the complexity of the project.

Has anyone else had this/worked out what is causing it because it is pretty irritating.

[Andrey_Dmitriev]

It could be the same root cause as reported here: "LV 2024 Q1 (64): Cannot save VI, no error message appears, just does not save", because " ...I try to save a VI that has changes, nothing happens.  No error message, nothing.  The asterisk remains on the title bar of the VI...". Something could be wrong with marking VI as "changed", then unable to save, the only slightly different use case. If you will found "minimal" project and steps, which will lead to reproducible behavior, then the half problem can be solved and someday fixed by NI.

[Worle]

 agree, looks like a similar issue, albeit subtly different.

The workaround which seems to be working for me so far is to right click on the class in the project and save the class. It Then comes up saying something like 'this item refers to unsaved items, do you wish to save them first'. That dialog then lets me save the offending VI's