If you happen to have required fields in tabs that are hidden or marked as cached, this will cause an issue with tab caching because the system wants those fields to be populated at the time when Personas attempts to read all cached tabs.
Imagine that in order to do tab caching, the Personas client will click on each tab header to read the tab's content. If at any given time during this process, an error message comes up complaining about required fields, this will result in failed tab caching.
In your screen shot it is visible that tab caching wasn't successful, so this has to be analyzed first why it happens.
So try to do manually what the system does. In the Basic View, click on the tabs that are cached and see if you get an error while not making any entry in any fields. If you do, that's the problem.
If you are not moving objects out of the Texts tab but you want to display it in its standard format, then don't cache it. You only need to cache tabs that you want to move objects out of (and sometimes the one you are moving these to). In general, keep tab caching to the bare minimum you need to fulfill your requirement.
If you merge fields from multiple tabs, do you still need the originating tab? If not, you can make it invisible.
Play around with this and see what's the result. If you still have a problem, post back.