Hi Steph

A fix for this has been developed TL-7181 and is expected to be included in the next release this week for 2.5.,2.6 and 2.7 - the issue reappeared after being fixed earlier.

regards