GroupShare 2017 ChangeAssignment API throws BadGatway error

Question

Hi 
 I'm attempting to change the translator for about 300 files in the same project and language. The ChangeAssignment call returns with a BadGateway error, but I can see in Studio that the changes were actually applied. I assume that this is some kind of timeout, but where (IIS)? Can this be increased? 
 The call works perfectly with a smaller set of file, e.g. 10. 
 I've tried 2 different client approaches, GroupShareKit and RestSharp. Both produce the same results. 
 
 Splitting the assignment into multiple calls does workaround the problem. I cannot use this approach though, as the translator will receive multiple emails. 
 
 Any ideas (other than improving the hardware)? 
 
 Thanks 
 Alan

Alan Anderson · Accepted Answer

After much research I've found that this is indeed an IIS timeout. The webfarm timeout is set to the default (30s). Increasing it to 5 minutes has fixed the error (why is assignment so slow?). 
 
The timeout can be found under webFarms on the IIS configuration editor. Open the GroupShareRestAPI farm then navigate to applicationRequestRouting/protocol/timeout.

GroupShare Developers > GroupShare Developers forum

GroupShare 2017 ChangeAssignment API throws BadGatway error