Hi Joshua,
I have just checked with the latest FEFLOW release (FEFLOW 7.5 - Update 1). It seems this was an old bug, which has been fixed already.
In case you have any question, I encourage you to get in touch with the official technical support mike.de@dhigroup.com
Cheers
Carlos