You’ve set a 3min timeout, which is pretty low. The example in the docs uses a 60min timeout, which is hopefully a bit long. But the point of waiting for a response instead of expecting one immediately (synchronously) is that other things could be going on on your server. Some projects take longer to process, server-side, than others and if you have one or two of those hit the queue before your project, then it could be a good bit longer than 3 minutes before your project’s analysis report is processed.
from my experience, a timeout of 10 mins is sufficient.
We use it for all kind of projects and never had any problems.
The only reasons for timeouts we faced were related to proxy / firewall permissions
when accessing Sonarqube from different network areas.