Hi Mahajan, There's nothing wrong with CONSOLE appender it's OOTB appender, when it gets triggered it means other configs for logs got messed up. Take backup of your instance,Open system console on slinglog page and compare your misconfigured log state with the OOTB instance config.Once you identify differences configure both same way. In case of issue restore from backup. Regards.Peter

Hi Gaurav, Great discussion. There's no one rule fit's all here. It all depends on the use case and tech stack you have. Preparing right url's upfront in AEM is a great beginning, to avoid any redirects in first place. Routing to correct url's via Apache is a solid way to go on from here. Where Apache lack's functionality or get's too complex, CDN / Varnish / NGinX will help. Once these are in place, redirects will be needed as project life goes on, they can be offloaded to the most appropriate ...

Hi Tarini, Yes, that's one way to solve it, Just keep the Service that know's it's state just a boolean, which is updated by the Job, so that it's near instant to know the state. Regards,Peter

Hi Tasunil, Expose API's to communicate clearly the status of the process. So that in case of a long running job you would be able to come back and check for status every few seconds.. This way you avoid long wait and have short nice calls into your core Job/Service connected to it. Regards,Peter