Skip to content

Commit ed9a28e

Browse files
authored
Merge pull request #26090 from microsoftgraph/mcm223-20250114-cr-notifications-update
Update call record change notification docs to clarify create behavior
2 parents a178064 + 5b98367 commit ed9a28e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

concepts/changenotifications-for-callrecords.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,9 @@ Content-Type: application/json
3838
}
3939
```
4040

41-
Change notifications for call records support both `create` and `update` notification types. A subscription for `create` changes only sends a single notification when a call record is first generated. A call record is created after a call or meeting ends and remains accessible for 30 days.
41+
Change notifications for call records support both `create` and `update` notification types. A subscription for `create` changes only sends a single notification when a call record is first seen on a particular subscription. A call record is created after a call or meeting ends and remains accessible for 30 days.
4242

43-
A subscription for `update` changes includes an initial notification when the record is first generated and any subsequent notifications as that record is modified. Because specific call record attributes depend on client-side signals, which can be subject to delays or interruptions due to network issues, a call record might undergo updates with new or revised information after its initial creation. These changes trigger an `update` notification, and the record's `version` field is incremented to indicate the modification.
43+
A subscription for `update` changes includes an initial notification when the record is first seen on a particular subscription and any subsequent notifications as that record is modified. Because specific call record attributes depend on client-side signals, which can be subject to delays or interruptions due to network issues, a call record might undergo updates with new or revised information after its initial creation. These changes trigger an `update` notification, and the record's `version` field is incremented to indicate the modification.
4444

4545
The latency of change notifications and the maximum subscription expiration period are defined in the [change notifications overview](/graph/webhooks).
4646

0 commit comments

Comments
 (0)