I reproduced the scenario and noticed that when the query is executed on release, the response time is faster than query executed on change activity. For this case, we've no issue.
When executed the query on change activity, the response time is slower and show the proxy error on browser. Please, can you tell me what is the problem that we are facing?
Answer by ShaneTan (16) | Aug 26 at 03:11 PM
The query on change activity is longer is probably because there are more internal work need to be done for the change activity. It should be normal behavior. Also you indicated that it is okay for you. But the longer query for change activity finally turned out timed out by the proxy server. On the server side there is no any problem from the server log, this is a behavior of your organizations proxy server. You configured the proxy server in your browser for the internet access inside your network, that is okay and necessary, but you should by-pass this proxy server for the DC access (because that is inside your network, you don't go to outside world for that). Because one, I don't think that you can request the proxy server timeout setting change, and two, some of the DC transactions is longer than one minute (I think your proxy server timeout is about 1 to 2 minutes), and in some specific building process, the DC transaction is much longer than one minute.
You can take a look of this link for more information about proxy server:
https://limeproxies.com/blog/how-to-fix-proxy-timeout-errors/
Why my Rule Designer is not responding? 1 Answer
Rules Missing After Building Using Maven? 1 Answer
Is there a way to configure my Eclipse to speed up the compile time? 1 Answer
Why the keyboard combinations not working when making RuleFlow Changes using MacOS 1 Answer
How to connect Rule Designer to Decision Center using personal certificate? 1 Answer