Interpret messaging activity history¶
Messaging activity history records selected conversation, channel, participant and message actions. It is separate from the messages themselves and from the delivered/read indicators shown in a conversation. Use it as supporting context when reviewing an action, not as a transcript or proof that every intended recipient received and understood a message.
Draft scope: this guide follows the inspected recording code. Complete messaging navigation, permissions, notifications, attachments, assistant journeys, Final Screens and connected delivery still need reconciliation. The entries described here do not establish that every messaging action is captured or that your environment is ready.
Understand the action¶
| Recorded action | What the entry describes |
|---|---|
| Start a direct or group conversation | Creation of the conversation, with the intended other person or requested group participants recorded as affected people. It does not mean a message was sent. |
| Create a channel | Creation of a conversation used as a channel. The affected list comes from the requested participants, not a later membership review. |
| Connect work to a channel | Creation or updating of the connection between work and a channel. It does not prove that related messages were subsequently delivered there. |
| Create a workstream thread | Creation or updating of a workstream discussion and its participants. It can describe additions to an existing discussion rather than an entirely new one. |
| Add or remove a participant | The acting person's membership action, with the selected person recorded as affected. Removal deactivates participation; it does not erase conversation history or earlier knowledge of its contents. |
| Send text or media | The message-creation action. A message containing both text and a file is recorded as media. The affected list contains other active participants at that time, not confirmed recipients. |
| Mark a message delivered or read | A status acknowledgement by the acting participant. It is separate from sending and does not independently prove human attention, understanding or completion of related work. |
Conversation and participant actions refer to the conversation. Sending and status acknowledgements refer to the individual message. Conversation names may appear where available; message text and file bytes are not copied into this dedicated activity entry. The full message, its attachments and its current audience require their own authorized access.
Repeated entries and unchanged status¶
Repeated delivery or read acknowledgements can produce another activity entry even when the message already has that status for the participant. The system keeps the existing status and can record the request again. Do not count these entries as distinct deliveries or reading sessions.
Removing an already inactive participant can also produce another removal entry when the person taking the action still has permission. Adding someone who is already active fails at the membership check. A request to create a workstream thread that finds all relevant threads and participants already present returns the existing result without creating a new activity entry in this path.
Connecting work to its existing channel can record an updated connection even when the destination is the same. These differences are why an activity count is not a reliable count of newly created conversations, newly affected people or completed business work.
People and recorded time¶
The person shown as the actor is identified using the profile available for the action. The affected people are selected separately: they may be requested participants, a person being added or removed, or other active participants when sending. Status acknowledgements and channel connections do not supply an affected-people list through this recorder. An empty list is not proof that nobody was affected.
The recorded time is taken when the action is being recorded. It is not necessarily the message's original send time, an earlier membership date or the time the history page received the entry. A saved actor name or email is a snapshot, not a guarantee that the current directory profile is identical.
An “all read” or “all delivered” message indicator is calculated against the applicable active participants when status is processed. It does not certify delivery to former participants, and the dedicated activity entry is not the calculation itself. Read and delivered acknowledgements are stored separately; do not infer one solely from an entry for the other.
Investigate an unclear result¶
- Return to the authorized conversation or work item and inspect the message, current membership or channel connection relevant to the action.
- Allow for separate history and conversation updates. A missing entry or delayed screen is not proof that sending or changing membership failed.
- Avoid resending a message or repeating a membership change solely to create history. Preserve the original attempt and visible result for support.
- Give authorized support the workspace, conversation, action, approximate time and visible result. Share message content or attachments only when necessary and authorized.
Managers should assess the underlying work and conversation context before interpreting activity totals. A completed recording result describes the logged action; it does not establish notification delivery, recipient attention, policy compliance or completion of the work discussed.
Continue with Review activity history, how recording works and follow a work-item timeline. Complete messaging task instructions remain a separate documentation continuation.