Hi everyone!
This week we retried this behavior, and looks like now it’s working as expected.
So, if you have metafields with some namespace/key, you can create a Metafield Definition afterward without any issue.
I hope this behavior now works as everyone expected. ![]()