Keith Stevenson Posted February 10, 2022 Share Posted February 10, 2022 @nasimg@sprasad - Not sure why you are still seeing the error. Have escalated to our general Support team to contact you and to check that its the same issue. KInd Regards Keith Stevesnon Link to comment Share on other sites More sharing options...
nasimg Posted February 10, 2022 Share Posted February 10, 2022 @Keith Stevenson - following the app reload (and removing the workaround), I can confirm patch is working for us. Nasim Link to comment Share on other sites More sharing options...
sprasad Posted February 10, 2022 Share Posted February 10, 2022 @Keith Stevenson - I removed the workaround and did a cache reload. Got users to clear cache and restart but the error persists. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now