Thank you for your answer.
I did not manage to reproduce the warning with a basic example of this… As our use case seems to not causing trouble, we will ignore this warn for moment.