Tooky,
That sounds like a sequencing issue. If one container has a template function that references another (for instance, with the NodePrivateIPAddress function) then that container must start after the one it references - otherwise the value won’t have been populated yet. This can be enforced with subscriptions - Marc’s written up how to use them here.