1-minute Send/Receive timeout is a problem on a slow connection

Question

I've tried send/receive a few times with a test project that I'm sure has minimal if any actual changes to synchronize (none from my end, probably none from the server end), but it frequently times out, and always at the 1-minute mark. I see that some of the data was downloading, so the timeout wasn't due to zero communication with the server, but instead it seems like there's a hard-coded timeout 1 minute after clicking "Send/Receive" regardless of whether there's anything actually being downloaded. If this is the case, I'd like to suggest that the timeout only apply to making initial contact with the server, and/or that it gets reset any time a chunk of data or packet is received from the server. There are still lots of people with slow connections (I was downloading at about 1 Mbps while observing this), and they will be very frustrated if there's always a timeout if Send/Receive doesn't finish within 1 minute. This would be even more of an issue if there are multiple projects to synchronize, which I often have to do as a project admin.

Answer 1

Thank you for this feedback. We are trying to find a good balance between reasonable timeouts that do not block users while preventing potentially unresponsive calls from blocking the application.
For now individually you can change the timeout setting from the app menu → Settings → General → Request Timeout (in seconds). To disable timeouts you can put it to 0.

Comments

Yes, thank you. I did later find the timeout setting and changed it to "90", but I didn't realize that "0" was also an option.