RPI v7.8 post-release product updates | Redpoint Documentation

Overview

This page provides detailed information about fixes and features that have been added to RPI v7.8 after its initial release.

Some patches require Helm chart updates, while others do not. This is noted for each patch version:

Image-only update: There are no changes to the Helm chart. You don't need to pull the latest chart version. Simply updating the container image tag within your existing values.yaml file is sufficient.
Helm chart update required: You will need to pull the latest Helm chart version. Refer to Managing Helm chart updates for self-hosted RPI v7 deployments for details.

This release contains Helm chart updates.

Fixed an issue where a Cheetah Digital email fulfillment interrupted and restarted part-way through its send treated already-started recipients as finished, while still reporting success. Unconfirmed recipients are now reported by identifier range and the activity fails, prepared content is retained across a restart, and send failures reported by the queue are no longer discarded. (Ref. 27965, 27964, ITDSK-29822)
Large Cheetah Digital email sends no longer load an entire audience's rendered content into memory at once, which could exhaust the Execution Service's memory and cause the run to restart and lose its audience. The send stage now processes a bounded number of content batches at a time. (Ref. 28037, 27964, ITDSK-29822)
Recipients rejected by Cheetah Digital because a triggered campaign was still being set up were previously abandoned without retry, with the activity still reporting success. Rejected sends are now retried with backoff over roughly a minute; any recipients still not accepted are listed by contact in the activity log with the provider's full response, and the activity fails if fewer recipients reach the provider than were targeted. (Ref. 27986, 27982, ITDSK-29822)

Fixed an issue where a Data Transfer activity (or an Export activity with Write Offer History off) configured to export data at a different resolution level than its audience would fail during execution with a "Join not found" error and produce no output file. (Ref. 28017, 28016, ITDSK-29934)

Fixed a defect where saving an audience, interaction, or other definition that had grown sufficiently complex could permanently fail with a generic error, blocking further edits. (Ref. 28027, 27952, ITDSK-29770)
Fixed an issue where an interaction using a Cell List block with a custom deduplication key could fail unpredictably depending on the order its sibling cell lists happened to run in. (Ref. 28082, 28065, ITDSK-30078)

Fixed an issue in the External Integration API where the "Name" field on workflow associations and workflow activities in the Interaction Tracker and Interaction Reports responses always returned an internal value instead of the actual name. (Ref. 28051, 28029, PS-258)

Channel synchronization tasks using Data Management could hang indefinitely when a Data Management job or report download stopped responding. These waits are now bounded, and an optional new setting (RPDMJobTimeoutMinutes) caps how long a Data Management job may run before it fails cleanly; an aborted Data Management job is now treated as a failure. (Ref. 28039, 28040, 28081, 28028, ITDSK-29964)

Fixed an issue where new RPI 7.8 deployments using Microsoft Entra ID single sign-on prompted for interactive login every time the desktop client launched, instead of reusing the cached sign-in as in prior versions. The default Helm chart setting for microsoftForceLogin has been restored to match RPI's original behavior (false). (Ref. 28108, ITDSK-30602)

Last updated: September 11, 2026