More meaningful error message instead of this one is coming soon with the major platform upgrades. But while we get there, posting a minimal version of your definition replicating this error would help us to troubleshoot it.
Computation can fail if the definition is too complex and takes too long to process or if it generates a lot of geometry which can cause problems. Our video tutorials can give you some ideas on how to improve your models.
@Joseph_Oster please keep friendly tone of this Forum, we at ShapeDiver are also a bit guilty in this case.
@dmwoodicd as I mentioned above, we are working on better error messages. In the meantime, more information about your problem will make it possible to solve, please share a minimal version of your definition.
I think we have solved this problem already through trial an error. Either the Rhino7 SubD components are not supported yet or these bump the computation time over the limit.
Great to hear that you managed to solve this. Rhino 7 with SubD is currently supported only on our test system. Let us know via contact form at www.shapediver.com if you want to give it a try. More details below: