You may want to post your code. Or at least a better screen shot of your code. The left hand and right hand sides of the code are cut off. And I have no idea why there is a large blue wallpaper image on the right hand side of the jpg.
Seeing all of the code may give a better idea of your architecture. You may want to look into some of the architectures that handle multiple loops. Producer/consumer or master/slave. Templates can be seen by selecting File/New ....
You talk about the main loop and the camera loop, but it is hard to tell where they are or how they interact. You only want to have the camera loops run if the camera is actually running and prepared to do something. If you get an unexpected error message, you may need to do some special code to reset the camera. That is what luizmenezesjr by putting code or not putting code into a case structure that executes based on the condition of the error cluster. If you have an error, execute the clear error code and issue any reset type commands if necessary, if you don't have an error, issue the commands that grab images. You actually don't have to unbundle the error cluster to get the error status, you can wire the error cluster directly to the selector node of the case structure. Or at least you can in LV 8.2
