Hi,
Sometimes when loading a Batch setup, due to one or some “problematic” nodes, the whole nodes tree is gone and only media clips loaded in the Batch schematic. The message show something like “……..error occur on node xxxx the process aborting……” (sorry I’m not with the system now)
Is there any way that I can manually delete those problematic nodes from file directory then load the setup in order to keep most of the other working nodes?
Greatly appreciate for any tip or help 
That’s very broad. Could be a number of things. The batch is text based so you could start digging in to the pyramidal relationship of nodes and the main schematic. Start a support call and engage those buggers in solving your issue or get into the weeds and share the problematic batch group with this group.
That sounds like you have Motion Vector Tracking somewhere, and Flame is notorious for “forgetting” those. It has been reported and ignored by ADSK for many years.
I always do an old skool save of the batch. On occasion they are life savers.
If only there was a way to cache those motion vectors to an Openclip…
Thanks for all the input and suggestion!
There’s no Motion Vector in this setup just plenty of boring Comp/Action/ModularKey/etc nodes.
In the end I spent about 2 hour to rebuild the Batch tree by referencing another similar shot and loading each main nodes setup from opt/Autodesk/clip/stonefs/<project_name>/Workspace.wksp to get 90% of the setup back.
Even thought the error message indicated which node has issue, after load and test, the setup works as normal. This is not the first time that I “almost” lost setup, especially during clients session when setup likely growing into complicate and messy, which is pretty annoying.
I will build a new “old school” habit that save Batch setup into a customized directory from now on~
Thanks again for all the suggestion and encourage from this great community!
Wish you guys the best luck and this kind of thing will never ever happen~
You don’t really need to save to a customized directory. It is saved to the project setups and they are archived when you archive a project. Unless you are Alan, they should be rather small because the media is not saved, only the nodes. I’ve made it a habit to just hit alt-save before I hit render.