Fortinet Support just told me
The bug seems to be fixed in v7.2.5 and it is scheduled to be released in late May.