Forum Discussion
Matthias
3 years agoNew Contributor III
Working with support on this it appears like a downgrade to 4.30 patch2 solves the issue for our case.
Support confirmed that they are working on this topic with high priority - as the downgrade workaround (as suggested by support) is not applicable beyond Jan 7th.
hirakangshu_nag
3 years agoNew Contributor
Hi,
What was the final solution of this issue??
Regards,
Hirak