Network Rendering Uses Startup HDR

[DMerz III]

Sent a render to the Network, it rendered overnight, spit back a render with the startup HDR instead of my custom HDRI lighting. This has happened to me several times, and it is a huge waste of time because I don't realize that it has done this until after the render is completed. It happens randomly, for me. There's no warning. Even when I hover over the thumbnail of the "job" it shows up correctly.

Just want to make you guys aware of this. If you have any tips of why this might be happening and what I can do to ensure it stops happening, that'd be great!

Thanks

[DMerz III]

I've since fixed the problem. But it is a weird bug to begin with.
I use Viewsets a lot, which for those of who are aren't familiar yet, is a camera saved with the environment settings. In fact, I only use viewsets because it works best with my workflow.

I keep my viewsets locked to avoid moving the camera unintentionally. This is tricky if you decide to update the HDRI. I've found if you link an HDRI file, you'll need to go to the viewset, unlock it, save it, and lock it again. Sometimes though, KS6 has not recognized that something has changed in the viewset settings, and does not "save" because it doesn't think anything has "changed in the parameters".

What was happening was, the viewset was showing me the correct HDR in the viewport, but when it packaged itself and sent the job to the network server, it did not include my HDR. I had to go into KS, unlock the viewset, relink the HDRI, change something in the camera settings (then change it back) so it recognizes that something changed, which prompts the (unsaved) next to the camera name. THEN, save the viewset again, and lock it.

Weird process, and wasted a lot of time. Hopefully this quirk is something that can be worked out.