With M.App Enterprise 2018 release (16.5) there are more built in validations on vector data during the import process. We encountered issues when the vector data's bounding box did not fit within the CRS (area of use).
This scenario could lead to problems during the cache creation process.
To solve this issue all vector datasets are now validated against the CRS area of use. You can spot problems with your vector datasets after importing right away. If you see a invalid vector dataset you get more information with a tooltip on the invalid symbol.
If there invalid datasets in your list you get a new button added to the list. If you click on the INVALID button you get a quick filter to all invalid datasets. (So you don't have to go through the entire list.)
The checks are also performed while using the invalid vector datasets in legends, overviews or vector sets. You can't add invalid datasets anymore.