After the work_item is done with the subprocess, the subprocess is completely shut down and the next work_item restarts it. Production Scenario: Each work_item is responsible for initiating a subprocess (with arguments specific to the work_item) of a program that can only have one instance running at a time. The “production” scenario described below. What I'm hoping to have is respected order of the work_items, but if one work_item fails, to have the loop continue regardless (simplified example attached). When “Use Dynamic Partitioning” for the Feedback loops is turned “on”, order is NOT respected, but if one work_item fails, the loop continues regardless. When “Use Dynamic Partitioning” for the Feedback loop is turned “off”, order is respect, but if one work_item fails, the entire loop fails. I need to loop over each work_item one-by-one using a feedback loop, respecting work item order. I'll give it a try today and run the TOPs process overnight for a stress test. I'll attempt pointing the HDA Processor to a different scheduler for appropriate error handling to see if I can gain access to a hook to tell the system to split out the stream on error, like I've done in the past with the Python Script TOP. I was able to bypass any raised errors caused by the Python Script by using a Split top to bypass the other TOP nodes in the loop in case of error (which seems to work well enough). I did put in a support ticket this morning for the ‘Expected array object’ error on a seemingly perfectly good OBJ ( Side Effects Support Ticket: #91349 ). In the actual production scenario it's an HDA Processor TOP that is raising the following error when attempting to read in an OBJ file- Error: Unable to read file 'SCREW HH GB-5782(M10-1.5 x 45).obj'.Įxpected array object (near byte offset 1, line 1, column 2) The error appears to happen inconsistently throughout the TOPs operation and the OBJs that the system hangs up on open fine via the File SOP, outside of TOPs.

Sidefx houdini fx 17.0.416 crack