Forum Discussion
Data Refresh Timeout Limit for P1, P2 and P3? Timeout Issue
- Anonymous8 years ago
Hi,
I found a workaround for this. Switching network connectivity from direct TCP to HTTPS results into data refresh not getting timeout after 2 hours. Now the refresh is running fine after 2 hours also and it is getting completed in 2 hours 30 min. Network protocol can be swicthed from dircet TCP to HTTPS from data gateway app UI or from config file.
Thanks for the reply.
What is the timeout limit in on-premises data gateway (Enterprise) if P1 premium capacity is present? I guess it is 4 hours as per Microsoft. Not sure.
It seems all refreshes which takes less than 2 hours are completing fine but beyond 2hours is timing out.
In your case, when did you face this issue?
The type of the capacity is irrelevant. The timeout settings are the same for P1, P2, P3. As you observed, it is effectively 2 hours. However it should be 5 hours according to the MS support. The bug fix is underway according to them.
- Anonymous8 years agoNot applicable
Hi,
I found a workaround for this. Switching network connectivity from direct TCP to HTTPS results into data refresh not getting timeout after 2 hours. Now the refresh is running fine after 2 hours also and it is getting completed in 2 hours 30 min. Network protocol can be swicthed from dircet TCP to HTTPS from data gateway app UI or from config file.