Tell users which layers are causing offline areas to fail

[L_OG]

My team regularly leverages offline areas in FieldMaps for Enterprise. Every other week, someone will create a FieldMap that is correctly configured for offline use (all layers shown as offline-ready), but the FieldMap will fail to create offline areas.

We can identify which layer is causing the problem by systematically removing/re-adding layers and trying to create offline areas again, but that is a time-consuming and inefficient process, especially in a map with many layers.

Sometimes we can get additional insights into which layer is causing the failure by looking at the Server Logs, but that requires someone with administrative privileges to look into the problem.

It would save a lot of time if an offline area "failed" to be created and returned a useful error in the offline map GUI that identifies which feature/features are causing offline areas to fail. This would allow non-admin users to more effectively troubleshoot their own problems. 

Ideally, the issues that are causing these offline areas to fail would be resolved instead, but I'd be happy to start by at least having more information to work from. 

[EricaNova]

I can't believe this isn't getting more likes.

Last Friday, I created 4 offline maps for my map project successfully. Then - bam - the last offline map wouldn't work. First it just hung, and then they would fail I tried everything - creating smaller map areas, removing layers, duplicating the map, nothing worked. Today (3 days later), I tried again and - surprise! The map area was created without issue. These failures were not my problem - nothing changed between the 4 successful offline maps, my failed ones, and my final successful map. This process needs to be a) less error-prone and b) more transparent. 

It makes it VERY difficult to rely on field maps for our team.