Personal opinion only, treat as such.
These NT packages seem to be standard offer, so I’d have expected that the settings in the inverter were dumped in from a file, rather than entered individually. That doesn’t entirely remove the possibility of an error being made, but does reduce it. That the same package behaves OK for others is also a warning.
In an ideal world I’d like to check the internal fault log, to see what the trip code was.
There will be options beyond current overload that can trip a VFD, for example I squared t – which may be downrated below a certain fraction of notional motor speed (I’ve been caught out by that one).
Whilst connected to check the log, I’d probably also monitor the reported motor current to check it is a sensible value, and not somehow higher than expected.
It’s easy to make a change with good intent, that either doesn’t help, or just masks the real problem.
This assumes that it is the VFD that has tripped, not some other protective device.