Hi, Robin


Since the timeout issue ( QB-3627) , I have been working on the following tasks.

1. Deleted quite a few old logs on each product node. ( that's because some node has a lot of build histories )
2. Paused the Cron Schedule build set on many nodes and changed the Build Condition from "if changes found in referenced repositories" to "always build".
This is because when the build condition is set to "if changes found in referenced repositories", it seems to be making more network traffic.
(It compares the latest commit & files on remote repository of github with the latest ones on the build agent. )

There was no timeout issue on the node that did the above two tasks.
Although this is not a perfect solution, I think above things I did can reduce timeout issues at least.

And I enabled cron schedule build on only one node. the read timeout issue occurs only in the node where the cron scheduler is configured.
Please see attached screenshots and log files from build agent machine.

Take a closer look at what more we need to do. this issue bother us a lot.