Known Issues · Marketing Cloud Automations
It is possible for an email to fail validation when using CSS .slot tags within the email. The email will fail to send with the error "No closing tag was found for the Guide tag block. Guide tag blocks must be closed by a corresponding close tag of the same name."
In Review ·Reported By 1 ·Updated Yesterday
When importing more than 500 subscribers from a file on the desktop into a list in an older account, the import may fail with no one imported.
In Review ·Reported By 7 ·Updated 2 days ago
Marketing Cloud Automations , Marketing Cloud Email Studio , Marketing Cloud Integrations , Marketing Cloud Journey Builder , Marketing Cloud Admin , Marketing Cloud Reporting , Marketing Cloud Sending
When exporting all opens for a Marketing Cloud Triggered Send, some records are not included in the file.
In Review ·Reported By 11 ·Updated 10 days ago
The Interaction Studio activities in Automation Studio only display folders rooted under the parent Data Extension folder. If there is a folder within a sub folder, you cannot select any objects from it.
In Review ·Reported By 1 ·Updated 11 days ago
Creating a recurring schedule on an automation for a data extension entry in Journey Builder may result in an incorrect or changing End Date in the UI Canvas details.
No Fix ·Reported By 2 ·Updated 2018-12-21
When setting up a Salesforce Import to an Object, you have the option to select the "Age of Import Data." If you select "Import All Data" and run the import, the import will run as expected. However, the Import Definition is updated to use "Import Modified Data Since Last Import Date" using the import's...
In Review ·Reported By 0 ·Updated 2018-12-10
Some Automation Studio executions may experience intermittent network connection issues resulting in disconnections. This relates to a specific set of errors that can only be found by raising a support case to confirm if this issue affects you.
In Review ·Reported By 3 ·Updated 2018-10-09
When 'CustomerKey' value of of Shared Data Extension (Enterprise Level) matches with 'CustomerKey' in any Business Unit's Data Extension, and when the BU's is used as Target Data Extension for a query activity, Queries gets parsed incorrectly to point to either Enterprise level or Member level randomly...
In Review ·Reported By 1 ·Updated 2018-08-31
When using MobilePush to send a Message to a Data Extension Audience, and that Message is using the Outbound - Automation Template, the Message is delivered but there is no Personalisation pulled against the fields referenced in the Message from the DE
In Review ·Reported By 4 ·Updated 2018-08-28
Fields that have a default value of emptystring() cannot be used in SQL queries. These fields are generally published as part of Audience Builder Data Extensions. They're not unique and generally not helpful in identifying anything for a subscriber or subset of subscribers. This problem arises when you...
In Review ·Reported By 2 ·Updated 2018-07-05
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.