Oracle Cloud Infrastructure Documentation

Reviewing Oracle Radio Channel Activity

Review communication activity that your Radio authorization allows you to access in a channel.

Activity views and history responses contain the records available to the requesting user. A loaded result isn't a guarantee of complete channel history or a subscription to future events.

The Radio app's history requests require radio.message.history. WebSocket GET_MESSAGE_HISTORY has no operation-specific permission handle; follow its linked prerequisites rather than substituting the REST permission. REST talk-status and connected-user queries require radio.channel.read. Playing stored audio requires radio.audio.read. Check each linked operation's requirements; REST and WebSocket checks aren't interchangeable.

Reviewing Channel Activity

  • You can inspect the activity available to your authorization without joining the channel. Opening an unjoined channel loads an activity snapshot; it doesn't join the channel or subscribe you to live updates.

    When recording activity is available, a completed transmission from another speaker can show Processing recording… while Radio waits for the final transcript. Radio checks channel history for the final result and resumes its checks after reconnecting. This is a processing state, not another live transmission or confirmation that a final transcript is ready. If Radio reports Processing is taking longer than expected, you can select Try again. For an access error or a result that remains unavailable, see processing guidance.

    1. In Radio icon Radio, select the channel that you want to review.
    2. Review the authorized communication entries in the channel workspace.
      No activity yet means the loaded result is empty. For Activity unavailable or Activity could not be loaded, see activity guidance.
    3. To review earlier entries, select Load older activity or scroll to the end of the loaded activity.
      The initial request loads up to 100 entries. Without an active Find query, scrolling near the end can load another page. Clear Find before loading older entries, then search again. If loading fails, select Try again; entries already loaded remain available.
    4. Use the displayed sender and time information to identify the relevant activity.
    5. To find an entry, open the Channel actions icon Channel actions menu next to the member count, and select Find.
    6. In Find in transcript, enter part of a sender's name or message text.
      The search ignores capitalization and filters only entries already loaded in the selected channel. It doesn't search all stored channel history.
    7. To show all loaded entries again, clear the search text or select Close find.
    8. To summarize loaded activity, open Channel actions and select Summarize.
      The app creates a local summary containing the entry count, the count of voice transmissions without transcripts, and up to three latest entries containing text. This isn't an AI-generated summary or a summary of all retained history.
    9. To save loaded activity as text, open Channel actions and select Download full transcript.
      Despite the action's name, the file contains only the currently loaded entries. The initial history request retrieves up to 100 entries. Use Load older activity before exporting to include earlier entries. Export doesn't automatically retrieve the remaining pages; 100 isn't a retention limit or a fixed maximum for the export. The file contains the loaded message and transcript text, not the audio recordings.
    10. For an individual recording, select its Play icon Play control to listen or its Download icon Download control to save the audio.
      Recording access is subject to your authorization and the availability of the recording. A displayed transcript doesn't guarantee that its audio remains available. No transcript available indicates that no text is displayed for the entry. The sender might have turned off server-generated transcription in Radio settings; this doesn't disable recording. The Browser App displays source transcripts without translation. See recording guidance.
    Radio shows the loaded channel activity available within your authorization scope, filtered by your search text when provided.

  • Use an authenticated connection and request only an authorized channel. Review the operation-specific history requirements.

    1. Send GET_MESSAGE_HISTORY with the channel and desired result limit.
    2. Process MESSAGE_HISTORY or handle ERROR.
      Review the returned records and any supplied hasMore value. Don't treat a limited response as a complete export.

    The client receives a history snapshot. To receive live channel events, follow joining channels.

  • This guide doesn't currently provide a REST channel-history procedure. Use the Radio app tab to review activity or the WebSocket API tab to request a history snapshot. The REST talk status and connected users operations report current state, not historical activity.

Reviewing the Mobile Inbox

Use Inbox in the installed Android or iOS app to review available text and voice entries. Received text and finalized voice entries retain their Critical Alert priority. This is different from the browser's channel-activity workspace. For foreground, background, and locked-device receipt, review the receiving prerequisites.

History and stored audio remain subject to the history permission, audio permission, and your channel access.

  1. Open Inbox.
  2. Select All, Received, or Sent. Use the grouping control to show entries by date or channel.
  3. Open the entry you want to review. Use its playback control when a voice recording is available. A transcript doesn't guarantee that its recording is still available.
  4. Use Mark all as read when you have reviewed the entries. Read status is local to this installation; it isn't a delivery or read receipt for other users.
  5. To remove local entries, use the entry's delete action or the Inbox clear/delete-all action, and confirm the displayed choice.
Note

Clearing Inbox messages removes copies on this device, not server history. Entries can return when Inbox refreshes from history. This action doesn't delete another user's copies or change the service's retention policy.

On Android, a history notice can indicate that only limited history is shown or that the last refresh couldn't confirm whether more history is available. Follow the notice to review browser activity when needed. A limited result isn't proof that older messages were deleted, and a refresh can recover older unread entries.

On iOS, Inbox retains the newest 500 entries across channels and message types. Received voice playback becomes unavailable eight hours after the message timestamp, but the entry and its transcript can remain in Inbox. This app playback rule doesn't apply to sent recordings and doesn't define the service's retention period. Recording access still depends on authorization and availability.

On iOS, an old received entry remains unread until you mark it read; audio expiry alone doesn't mark it read. Opening an unread entry marks it read even when its audio can't be played. Saved read markers are restored when you sign back in to the same server and account on this installation; they aren't read receipts or synchronization between devices.

If refresh or playback fails, see Inbox help.

How Inbox Uses Oracle Radio APIs

Inbox combines communication received by the app with history returned by the service. Filters, grouping, read flags, and removal of local copies are app behavior; they aren't interchangeable server operations.

  • A connected client receives live messages for its joined channels. GET_MESSAGE_HISTORY requests a channel-history snapshot; it doesn't mark Inbox entries read or delete them. Receiving a live message doesn't guarantee that it was saved to history.

  • The supplied mobile applications use REST history requests to populate or refresh Inbox. A history response isn't a read receipt or a delete operation. This guide doesn't provide an additional REST Inbox procedure; the REST reference lists the documented operations.