Hi @Johan_Velthuizen,
We’ve addressed this error. Please update to 3.0.28 and let me know if this persists.
