Loading

Old In-App messages getting displayed

Veröffentlichungsdatum: Jun 9, 2026
Beschreibung

This is expected system behavior. In-App message payloads are stored locally by the Mobile SDK once downloaded. Pausing or stopping the journey prevents new users from entering but does not revoke or delete content already cached on devices. There is no server-side recall mechanism for previously downloaded In-App messages.

Lösung

Workarounds and mitigations:

1) Set an explicit expiration for In-App activities in Journey Builder to limit post-pause visibility.
2) For time-bound or sensitive content, use short expiration windows that align with offer validity.
3) If an offer must be revoked, publish a follow-up app release or configuration that prevents the in-app trigger from matching, or deploy a replacement In-App with immediate expiry to supersede cached content where applicable.

Nummer des Knowledge-Artikels

005386569

 
Laden
Salesforce Help | Article