In AEM cloud, we don’t have access to system console except package manager.

Yes checked in publishers. It also redirects. 

We don’t add anything in dispatcher server. Only we use the page properties for adding the vanity url. Since it is a AEM cloud we cannot check the crxde. We checked the page properties by downloading the page and it doesn’t have the vanity url path. 

Tried clearing dispatcher cache but no luck. Somewhere the vanity url path is stored and it is not getting cleared. 

Actually, I achieved this scenario by adding parsys for each filter where I can add any modules to show under each filter. It was working as expected.

@SantoshSai In the generic use case, it's working. In my case, it's not working.

@SantoshSai My Apology. I forgot to add the exact code. I have modified the code above. Please have a look. And by the way, there is no specific error in the error log.   Just getting this - "org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.api.resource.ResourceNo...

The tooltip issue was resolved by adding a forward slash in front of the class.  <div class=\'sec-secondary-headings\'><h3>20% off on Mobile Devices</h3></div><div class=\'sec-paragraph\'><div class=\'p3\'><p>Coupon Applied: <b>SALE50</p></div> </div> Thanks, everyone for the help.

Thanks @Mohit_KBansal for your reply. The error was resolved but the encoded HTML did not show the content. The tooltip box is empty, showing white space instead of content.

Okay @arunpatidar Let me try but can you please explain to me what's the js code issue.