In talking with some of the Engineering folks, during the initial sync the transmit configurations are not yet active so there is a default timeout used which they believe is 30 minutes and would explain the behavior you are seeing.
One thought would be to disable that table to complete the initial sync and then enable it for the second sync where the transmit config timeouts will then be in effect and allow for the additional time needed.
Perhaps you can create a pre-built client with the data already loaded to avoid this for your users on their initial sync.
--Bill