The Sharepoint Reader and SharepointOnlineConnector have hard-coded timeout values which aren't always suitable. FME 2020 + increased the timeout value from 20s to 60s but it's still hard-coded. It would be great if the reader and connector could expose the timeout value as a parameter so that it's user-configurable.
Archived
Sharepoint Reader timeout parameter
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
Hi Nic, thank you for suggesting this idea!
Could you share more details about the scenarios in which you would want to increase the time-out for the SharepointOnlineConnector to more than 60s?
SharePoint Online is a cloud-hosted service for which I generally would expect rather low response times. I am aware that there are some reports about higher response times particularly for SharePoint Online (e.g compared to OneDrive), but I would still need some more details to understand whether more than 60s time-out limits would be useful.
During which action (List, Upload, Download) did you encounter the limitation?
Where proxies involved in the scenario?
Thanks
+20- Contributor
Hi Gerhard,
it was a little while ago that I encountered the issue so I don't remember exact details but I believe it was using the SharepointOnlineConnector with the action set to "Download".
I was running through a list of up to several thousand file downloads and a handful of them would fail with a timeout. Re-running the workspace for just the failed downloads would usually be successful but it would be good to be able to set a longer timeout and avoid this issue in the first place.
Thanks.