StatusFrequency
The StatusFrequency element represents the maximum timeout value, in minutes, in which retries are attempted by the server.
<StatusFrequency/>
SubscriptionStatusFrequencyType
Attributes and elements
The following sections describe attributes, child elements, and parent elements.
Attributes
None.
Child elements
None.
Parent elements
Element | Description |
---|---|
PushSubscriptionRequest |
Represents a subscription to a push-based event notification subscription. |
Text value
A text value that represents an integer is required if this element is used. The possible values for this element are 1 to 1440, inclusive. This element is optional. The default value is 30 minutes.
Remarks
The StatusFrequency value is used by the server to retry a push notification when it does not receive a response to a push notification or status ping from the client. If the server does not receive a response, it retries sending the notification several times before it stops sending the notification. In EWS, the default retry interval is 30 seconds and subsequent retries are always double the time of the last retry interval. Retry times are not exact as they can be delayed due to other loads on the server. The following table shows how the retry intervals occur in the 30 minutes allotted by the default StatusFrequency value (assuming the server did not encounter any delays).
Retry | Seconds | Time |
---|---|---|
0 |
0 |
Initial sync |
1 |
30 |
00:30 |
2 |
60 |
01:00 |
3 |
120 |
02:00 |
4 |
240 |
04:00 |
5 |
480 |
08:00 |
6 |
960 |
16:00 |
7 |
1920 |
32:00 - StatusFrequency default value of 30 exceeded, retry not sent |
If the client does not receive notification messages from the server for a period of time that exceeds twice the time specified by StatusFrequency, the client should take an action such as recreating the subscription.
The schema that describes this element is located in the IIS virtual directory that hosts Exchange Web Services.
Element information
Name | Value |
---|---|
Namespace |
http://schemas.microsoft.com/exchange/services/2006/types |
Schema name |
Types schema |
Validation file |
Types.xsd |
Can be empty |
False |
See also
피드백
https://aka.ms/ContentUserFeedback
출시 예정: 2024년 내내 콘텐츠에 대한 피드백 메커니즘으로 GitHub 문제를 단계적으로 폐지하고 이를 새로운 피드백 시스템으로 바꿀 예정입니다. 자세한 내용은 다음을 참조하세요.다음에 대한 사용자 의견 제출 및 보기