I suspect the problem emanates from the anisotropic node. Cycles removed that node from the latest version of their render engine. Instead they use the Glossy node to perform both normal gloss and anisotropy.

We setup SuperFly to automatically replace the legacy anisotropic node the new implementation. Basically we just plugged the old connections into the new node. The intent was to not break all the shaders that used the Cycles anisotropy. Clearly we missed something. The test cases we were using didn't fail.

I've responded to the support tickets submitted with this as well. Now we have to fix what Cycles broke.