Salesforce Known Issues
Trailblazer Community

Known Issues · Marketing Cloud Email Studio

Reply Mail Management auto-reply FROM NAME from an auto-reply triggered send shows the email address instead of the display name.

Marketing Cloud Email Studio

When setting up an auto-reply triggered send the FROM NAME uses the email address instead of the FROM NAME. This occurs in both ERMM and RMM.

In Review ·Reported By 8 ·Updated 9 days ago

Unable to schedule a Marketing Cloud Prebuild Burst Send properly

Marketing Cloud Email Studio , Marketing Cloud Sending , Marketing Cloud Content Builder

Currently, when using the Send Flow to schedule a Prebuild Burst email send, the time (and not the date) will only be used to start the send. For instance, scheduling a Prebuild Burst send on 11/29 at 12pm to start sending on 11/30 at 9pm will start the send on 11/29 at 9pm.

In Review ·Reported By 0 ·Updated 9 days ago

Creating an email activity in a Journey with the same name as an existing Journey will place the triggered send in the first Journey's folder.

Marketing Cloud Email Studio , Marketing Cloud Journey Builder

If a new journey is created with the same name as the first journey and activated the email activity's triggered sends are created in the same folder as the original triggered send.

No Fix ·Reported By 1 ·Updated 10 days ago

Unable to delete Profile Attribute used in Business Unit Filter

Marketing Cloud Email Studio

When a Profile Attribute is used in a Business Unit Filter, and the Filter is then removed and Profile Attribute is deleted, the Profile Attribute errors when trying to be deleted.

In Review ·Reported By 3 ·Updated 11 days ago

Unable to create new Primary Key field on Data Extension

Marketing Cloud Email Studio

Users may be unable to create a new Primary Key field on a Data Extension after using the Clear Data button more than once when configuring or changing a Data Extension.

In Review ·Reported By 34 ·Updated 22 days ago

Email studio reports configured to be sent via email may not be received

Marketing Cloud Email Studio

Email studio reports configured to be sent via email may not be received

In Review ·Reported By 5 ·Updated 25 days ago

Adding primary keys to the source DE does not reflect the primary key in the filtered DE.

Marketing Cloud Email Studio

Adding primary keys to the source DE does not reflect the primary key in the filtered DE. You can see the primary keys were added properly in the UI, but it were not actually created.

In Review ·Reported By 4 ·Updated 25 days ago

InvalidFieldCount error is thrown when system generated reports are imported to Data Extensions

Marketing Cloud Automations , Marketing Cloud Email Studio , Marketing Cloud Reports

InvalidFieldCount error is thrown when system generated reports are imported to Data Extensions because of two blank rows present at the end of the CSV files. This is a known issue with SQL Server Reporting Services itself in CSV files. This is a false alert for the invalid field count error, as all...

In Review ·Reported By 1 ·Updated 25 days ago

Contacts Without Channel Addresses Data Extension Fails on Random Split

Marketing Cloud Email Studio

The Data Extension (DE) that gets created as part of the "Contacts Without Channel Addresses" Extract cannot be split without first modifying the DE properties. This issue can occur with other data extensions, but is more prevalent in this particular DE.

In Review ·Reported By 1 ·Updated 25 days ago

API calls to Email or SMS Triggered Sends can intermittently fail with timeout error

Marketing Cloud Email Studio , Marketing Cloud Journey Builder , Marketing Cloud API , Marketing Cloud Mobile , Marketing Cloud Sending

API requests to Transactional SMS and Transactional Email Triggered Sends may intermittently fail to complete, returning a "An unexpected error occurred while attempting to queue the send" error response.

In Review ·Reported By 0 ·Updated 29 days ago

Prev | 11 to 20 of 325 | 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.