Hi Alastair,

No, we upgraded to 2.5.5 on Monday and it appears to be resolved.

Thanks.