changeOrder API hangs

Cause

Customer scenario : coded WAIT for SelectMethod of changeOrder API. The Default value of this attribute is NOWAIT.

If you pass the value of this attribute to WAIT then the SELECT SQL fired by changeOrder API will have to WAIT to get a lock. It will not timeout.

The impact of setting SelectMethod to WAIT will be changeOrder call will wait instead of failing. The wait time depends on how long the original transaction holds the lock. As soon as original transaction releases the lock changeOrder then will acquire lock and process the record.
If you take care of sequential amendments then there will be very less chances of deadlocks.

However, we have a property which we can control the query timeout value. You may consider to use one of the following properties if you feel that it will help you if you decide to use WAIT as the attribute.

If you are calling changeOrder API from agent then you can use property
yfs.agentserver.queryTimeout

If you are calling changeOrder API from UI then you can use property
yfs.ui.queryTimeout

Please refer to properties guide for more details on above properties.