As others have already said, the "run continuously" button has no valid purpose in a toplevel program. It is actually named somewhat misleading, because what it really does is restarts the program automatically whenever it finishes.
Any bigger program consists of serveral stages, e.g. Initilizations where conditions and hardware are configured, memory allocated, files are opened, Main where the actual purpose takes place, handle operator input, display results, etc., shutdown where things get cleaned up, references closed, etc.
Usefull tools such as the "First run?" function loose all meaning during "run continuously". Also event structures don't work well in this mode.
Sure, if you are just started learning labview and just want to e.g. add two numbers (for example) you are allowed to use "run continuously" 🙂 It does not matter that the program uses 100% of the CPU doing mostly the same calculation over and over (and over and over...) again. However, in the second lesson, you should learn about loops an use them from then on. 🙂
One valid use for the run continuously feature is for example if you need to debug a subVI which does not contain a while loop. Using the "run continuously button" will allow you to quickly play with a series of input values while observing the result, probing the diagram, etc. It is one of the cool features of LabVIEW that subVIs can be run independenly without any need to write e.g. a primitive test caller.