@davidjgonzalezzzz the AEM 6.5.8 release notes mentions that this issue is fixed. We do have a AEM 6.5.8 instance running and are still facing this issue, could you please let us know if there is any update on this ? Is the above fix applicable for AEM 6.5.8 too ?