After much experimentation it seems PG does a good job of managing repeated areas on the first level, but it does not know how to deal with nested definitions under a Repeat Area.
This wouldn’t be an issue if you use unique names for each area definition within the component (as you should), but when any of these areas are nested within a repeatable area, things go askew.
Say you have nav component, and you want to allow for adding menus in your component by including an optional and repeatable area (to add the menus).
each menu is going to be a duplicate of the one before it and use all the same field id names. PG gets weird about that as soon as you hit the Update button.
(btw, apologies for all the extra spaces, my keyboard is behaving badly)
Win7(still) and PG5.96