Mesh is not closed Warning

[bernd.brinkmann.mail]

Multiple mesh bodies in separate projects I have been working with suddenly developed this warning. 

The mesh repair function does not progress even after a night run and the mesh does not need to be closed since I only generate a toolpath using its top side. Now if I generate a toolpath it still looks fine and does visualise as expected. 

However if I want to post process the toolpath it is empty and simulating it is also not possible. 

Nothing on the system or the project has changed as far as I am aware. 

Any pointers would be greatly appreciated. 

[jeff_strater]

This is just an informational warning.  If you are OK with the mesh not being closed, you can just ignore it.

[bernd.brinkmann.mail]

Thanks for your answer Jeff. 

Its just that the empty tool path problem coincided with the appearance of this warning which led me to believe that it was the cause.

The tool paths generate fine and have no warnings or errors showing up, but once I try to post process them I get an empty g-code file. I tried rolling back to an earlier version of the project and reinstalling Fusion but no change. 

[jeff_strater]

Sorry, I'm not a toolpath expert.  @seth.madore may be able to help you, but I don't know his availability.  Do you have an example model that you can share?

[bernd.brinkmann.mail]

Unfortunately I cannot share the model. I will try to make a small example project later. 
I just did a fresh install of fusion 360 on another computer and I have the same Issue. A tool path that I post processed successfully last week is now apparently empty. Even though I did not regenerate it or change anything else on the project.

If I click on tool path data I can see the x y and z movements as expected. so the tool path is definitely not empty. 

[bernd.brinkmann.mail]

Update:

The reason why my toolpath were not working anymore was due to the fact that they were in a pattern. I took them out and it worked. I am still not sure what the actual issue is but at least I can post process a toolpath again. The frustrating thing is that this happened without any user input I am aware of. 

[seth.madore]

Yep, the Pattern issue was going to be my first guess. This is fixed in an internal build, which (hopefully) will be hitting the general public in the not-too-distant future