You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The comments say:
"Second, it would be nice to be able to specify an overall maximum polling duration, after which it could throw a time out exception.
Third, from my experiments it seems that the original HTTP request will time out in just under 90 seconds. It would be nice to be able to control that timeout duration with another property on DurableHttpRequest."
Here are some solutions to this issue:
An additional property (e.g. maximumPollingDuration) can be added to DurableHttpRequest to keep track of an overall maximum polling duration.
An additional property (e.g. timeOutDuration) can be added to DurableHttpRequest to specify if there is a custom timeout duration for the original HTTP request.
The text was updated successfully, but these errors were encountered:
These changes resolve#1278 by adding a `Timeout` property to `DurableHttpRequest`. This property defines the timeout for each individual HTTP request. This timeout applies to each asynchronous polling request too.
This issue is pulled from a comment made in the "Allow custom polling behavior in CallHttpAsync() for long-running endpoints" issue.
The comments say:
"Second, it would be nice to be able to specify an overall maximum polling duration, after which it could throw a time out exception.
Third, from my experiments it seems that the original HTTP request will time out in just under 90 seconds. It would be nice to be able to control that timeout duration with another property on
DurableHttpRequest
."Here are some solutions to this issue:
An additional property (e.g.
maximumPollingDuration
) can be added toDurableHttpRequest
to keep track of an overall maximum polling duration.An additional property (e.g.
timeOutDuration
) can be added toDurableHttpRequest
to specify if there is a custom timeout duration for the original HTTP request.The text was updated successfully, but these errors were encountered: