Hey @IronicParadox
Thanks for flagging this issue! We have actually resolved this issue internally, however it still needed some additional testing. We are aiming to have the fix included in the next hotfix for 5.5. Unfortunately, I do not have a timeline for that at this time.
Thanks again!