Salesforce Known Issues
Trailblazer Community

Known Issues · Marketing Cloud Mobile

MobilePush stats delayed in User Interface

Marketing Cloud Mobile

Sometimes the open/sent data can be delayed from appearing in the MobilePush user interface. This impacts the stats in the Overview section and within the Activity Log when clicking on an individual message.

In Review ·Reported By 6 ·Updated Yesterday

Responding to Outbound Message does not trigger Text Response for Next Keyword when replying with y, n, or yes

Marketing Cloud Mobile

After receiving an Outbound message configured with a Next Keyword, the expectation is that a response to that message will be appended with the Next Keyword and will trigger a response from a Text Response message setup for that keyword. However, it has been observed that this does not happen when responding...

In Review ·Reported By 2 ·Updated 2 days ago

SMS Account Summary report does not run at enterprise when Include Child Accounts = True

Marketing Cloud Mobile

The 'SMS Account Summary' report does not run at the enterprise level, when Include Child Accounts = True and some Child BU's are not using MobileConnect.

In Review ·Reported By 3 ·Updated 9 days ago

Journey Builder Decision split fails using MobilePush Demographics Attribute Group

Marketing Cloud Journey Builder , Marketing Cloud Mobile

When using the MobilePush Demographics Attribute Group within a Decision Split within Journey Builder, Contacts may show as failing within History once activated and injected.

In Review ·Reported By 3 ·Updated 20 days ago

Mobile number of deleted contacts still visible in _SMSSubscriptionLog

Marketing Cloud Audience/Contacts , Marketing Cloud Mobile

Due to orphaned records still remaining in some backend database tables, the mobile number of some deleted contacts will still be visible on the data view _SMSSubscriptionLog after the contact is fully processed via Contact Delete. These records will be listed in _SMSSubscriptionLog with the SubscriberKey...

In Review ·Reported By 4 ·Updated 2021-03-30

Personalization is not rendered in Push Inbox CloudPage when opened via alert notification

Marketing Cloud Journey Builder , Marketing Cloud Mobile , Marketing Cloud Pages/Sites , Marketing Cloud Sending

Since the April 2019, it has been possible to use fields from the entry source data extension to personalize the CloudPage content sent as part of a Journey Builder Push Inbox send: https://help.salesforce.com/articleView?id=mc_rn_april_2019_mp_jb_entry_source_personalization.htm&type=5 However,...

In Review ·Reported By 7 ·Updated 2021-03-27

Automated emails about p12 certificates expiring

Marketing Cloud Mobile

MobilePush sending has already been migrated to Auth keys. However, automated emails about their p12 certificates expiring are still being sent. It should not be sent for apps which are using p8 auth keys.

In Review ·Reported By 10 ·Updated 2021-03-17

MobileConnect Filter lists do not retain selected short code-keyword population

Marketing Cloud Audience/Contacts , Marketing Cloud Mobile

MobileConnect filtered lists do not retain the selected Short code-keyword population and defaults to All Contacts. If you create a Filtered List in MobileConnect and select a Short code- keyword as the starting population, the list created is wrong because the Short-code Keyword filter starting population...

In Review ·Reported By 0 ·Updated 2021-03-16

Refresh filtered list fails caused by intermittent issues

Marketing Cloud Automations , Marketing Cloud Audience/Contacts , Marketing Cloud Mobile

Refresh filtered list executions may experience intermittent connection issues. If this occurred during the mobile message sending process, it possibly resulted in not being sent messages This relates to a specific set of errors that can only be found by raising a support case to confirm if this...

In Review ·Reported By 1 ·Updated 2021-03-15

/sms/v1/automation/importSend returns an error using V2 Token

Marketing Cloud Automations , Marketing Cloud API , Marketing Cloud Mobile

When using a V2 Token to authenticate for the REST API, using the /sms/v1/automation/importSend route will return an error

In Review ·Reported By 3 ·Updated 2021-03-11

1 to 10 of 93 | Next

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.