Listing a few scenarios where exception handling works different that I expected:

1. When using an aggregate to get data, if the app is offline, the aggregate will generate a CommunicationException. It seems it is not possible to catch this exception in the screen in order to show an alternate content, instead the Exception propagates to the Flow where the screen is contained.

2. Using a DataAction with an aggregate inside to get data and an Exception handler next to the aggregate. If the app is offline, the aggregate will generate a CommunicationException and I expect the Exception Handler to catch it so I can show an alternate content. Instead the Exception propagates to the Flow where the screen is contained. Is this normal? 

3. Using a DataAction with a ServerAction inside to get data and an Exception handler next to the ServerAction. If the app is offline, the ServerAction will generate a CommunicationException and I expect the Exception Handler to catch it so I can show an alternate content. Instead the Exception propagates to the Flow where the screen is contained. Is this normal?

4. Using a Button calling a ClientAction with a ServerAction inside to get data and an Exception handler next to the ServerAction. If the app is offline, the ServerAction will generate a CommunicationException and the Exception Handler will catch it so I can show an alternate content. The Exception does not propagate to the Flow where the screen is contained.