We have discovered a serious bug in FileMaker Pro Advanced 17.0.x on macOS Mojave 10.14.2.
A very simple script with a simple "Sort Records" script step will freeze all of FileMaker 17 with the spinning beach ball, and the only option that users can take is to force quit out of FileMaker 17 altogether.
The exact same "Sort Records" script step works just fine in FileMaker Pro 16, but as soon as you try the same script step in FileMaker 17, it freezes up FileMaker 17 altogether.
This only happens in a scenario where FileMaker Server 16.0.3 is hosting the database (Windows Server 2012 R2). It does not happen when the database is opened locally.
The "Sort Records" script step is trying to sort on a related field in another table. The related field is an unstored calculation which references several other related fields in several other tables.
We can give FileMaker Inc. remote access to this file, or get FileMaker Inc. a copy of this file to see this bug in action.
(The only option we have right now is to use FileMaker Pro 16 as our client app... this is our temporary workaround for the time being.)