@BenJR, This is a known issue. Here is a link to a similar topic:
The issue should be fixed in the next release 1.15