The above condition returns a boolean after checking but the custom wait activity expects a dateTime value.

@SatheeskannaK - This logic will check whether the date matches and return boolean value like true or false but it won't return the date.

@SatheeskannaK - Thanks for sharing this. But I don't see the correct logic used in those threads. Can you help me with that if possible ?

We do have that in place but like this I have multiple conditions in the same journey. So, we need adjust the wait days accordingly with segment logic and the evaluation as well. It would be better using dynamic wait steps in the journey for all the profiles.  

We can't use addDays function in the condition. This is a great feature but not available in wait conditions.

@DavidKangni @AnkitJasani29  - The issue is resolved now. The issue is with the profile snapshot not updated with the time-zone values for many days.Finally, the value is added and able to use it but not sure why it took more than a week to add the time-zone field. Thanks!

@AnkitJasani29 Enabled this already 

Thanks for the response @DavidKangni  I tried using the similar approach as well but still I don't see the journey is recognizing the profile time-zone of the user. The journey considers the default time-zone that is given in the journey property.

Thanks for sharing this information @SatheeskannaKMuch appreciated.  

@SatheeskannaK - Thanks for the response. Will the new update gives us the option to link the form details including text fields to the respective profile? Or the option to map the form fields against any dataset in AEP directly and store as a response?Any idea, when we can expect the feature being ...