If you experience a lot of requests (from the piplanning server to the ALM-tool) running into a timeout, you cain raise the default values. This can happen if your ALM tool is painfully slow (We experienced that multiple times with Jira).
Edit the configuration file of pi-server in the on-premise-docker piplanning.cfg (>= v1.0.10)
Edit the piplanning.cfg file and set:
Where the integer (or float) value to the right is the timeout in seconds. If you set the value to 0, the default timeouts are used.