I have a 'Wait by Attribute' in my Journey which is referring to a date attribute in a data extension from contact builder. I then have a SQL criteria to change the Date values based on certain business rules.

I am expecting the Wait by Attribute to honour the new updated date values instead of the one it was referring to initially when contact made it to this Wait by Attribute activity.

The documentation on this activity is limited and doesn't explain much. Is this possible? if not, is there a way to handle this scenario in Journey?

Thanks, Mano

1 Answer 1


If the attribute you're using as the basis for your Wait By Attribute activity is within your "Journey Data", the value is immutable and no update to the underlying Journey Entry Data Extension done with SQL after injection would be taken into consideration by the activities within the Journey. If the attribute you're using is taken from your "Contact Data", updates to the field in question are reflected as the contact progresses through the Journey.

Once the contact has entered the wait, the date and time of exit is fixed. In other words, updating the field used by your Wait by Attribute will have no effect on when the contact exits the wait.


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .