My client wants to send SMS to campaigns in Salesforce. The send creates a Task, which is later updated in the journey with a status of SMS Delivered or not.
A campaign send can be created on a Friday to be delivered after 2pm the next Monday (or any working hour decided by the agent). This is done by setting the due date and time while creating the SMS send in Salesforce.
So I am using Salesforce as the entry source (Task object) and a Wait by Attribute that should hold the SMS send until the due date:
Yesterday in the afternoon I scheduled a send for today at 9AM, but the SMS was sent at midnight so it ignored the time. In the Data Extension related to the journey it shows that:
We're migrating the SMS sends from another system and the scheduling works there.
So my question is if it could be an issue with how Marketing Cloud reads dates from Sales Cloud or if it's some limitation with Wait by Attribute activity? Or something else that I am missing.
Edit: one possibility is that the problem comes from Due Date in Tasks being a Date format, not a Date/Time. Any advice is appreciated.