Just checking for any updates on this. Having the same issue in 2.28
Are you using the latest build of 2.28? if yes, maybe the fix wasn’t included… you may want to upgrade to a newer version since they have the fixes incorporated in the builds.
Hi @jomutsani, we are using one of the recent builds of 2.28 but not the latest, unless the patch was added sometime after January, I think the issue still exists.
We have just upgraded to 2.30 and the issue does not exist anymore.
Great news! Thanks for your feedback!