HTL/Sightly Exception Handling - to support a smoothly degeneration of a Page being on display in case of a single AEM/Sling Component fails Hi,I'm neither a Sling nor an AEM Genius. We want to migrate from CQ 5.6.1 with JSPs to AEM 6.2 with Sightly and Sling Models.I have this wishful thinking, and maybe I'm too blind to see, but a central feature seems lacking to me in HTL, which is the smooth degeneration of a Page if one of the Components (either being on a parsys or hard coded in the templates) is running wild (during initialization, or during the rendering of actual content - using either the Use or Sling Models API, of which the content typically gets cached for a certain amount time in the Dispatcher Cache - at least for us).I spent quite some time searching on the AEM forum and the internet for a suitable solution - without results, so I decided to ask this question as a "last resort".Typical to an enterprise scenario combing JCR with none JCR Backends, it is likely to happen sooner or later for external content integration (REST-, SOAP-API, DB Access), that it fails upon actual data retrieval, due to some unavaila