Image automation and policy, limit to namespace?

[ehrnst]

Hi. Is there a hard limit for image policy and update automation to be in the same NS?
I tried to design a setup for our apps where, gitrepository and imageAutomation where in flux-system and policy as overlays per environment/app in their respective namespaces. Everything worked out, except git updates. When i moved image automation to the app namespac, where the policy lives, everything worked.

i know this sentence The ImageUpdateAutomation API defines an automation process that will update a Git repository, based on ImagePolicy objects in the same namespace.

but given we specify namespace where the policy exists i figured it will work, like so # {$imagepolicy: <namespace>:<policyname>:tag}