Hasta La Motion!

Is there a way to force a node to be (re)evaluated? I’m having some trouble getting the first frame of a batch to render correctly, yet each subsequent frame works fine.

We have a custom node on which setting one value changes another. After wrapping it in a gizmo and exposing both values it all seems fine until it goes to render and the result isn’t coming back until the frame changes. (Or at least that’s as far as I can figure out). Just wondered if anyone here had seen anything similar.

Cheers
Ian