Hi Kim,

This issue should be fixed in release 1.3.17. Please let me know how it works out for you.

Thanks, Frank