hi @Raul_Albuquerq ,   Yes, you can use 0 in delta. It would simply return the current data and time with no change.   Warm Regards, Reena John

Hi @Poornaraj_Duraimani     Adobes response to the issue -  One guardrail/limitation is that when an event with a supplemental ID is used, all downstream events should also use a supplemental ID of the same namespace.   As we have more than one events in the journey and only one of them has a supple...

Hi @AJODev    You could do this both ways - Segment UI Builder and PQL. It would be easier to build this on the Segment UI builder using below steps.   Segment UI Builder : 1. Add an attribute say lastQualified in profile level that does the 90 day check. For this you can use Computed Attributes or ...

Hi @Poornaraj_Duraimani    Can you try to uncheck allow reentrance checkbox on the journey details and see if the error goes off. We tried and it hasnt worked for us. This seems to be an issue on the supplemental id, we are also facing the issue and have reached out to Adobe support team on the same...

Hi @ButhpurKiran  ,   Yes, we had faced similar issue and had raised an Adobe ticket to have Adobe check on this. The data volume that we had was huge and that was causing the delay in realization. Try and optimize the data that is being ingested using the Edge Merge Policy. If you still persist to ...

@RS195 , the supplemental ID feature works only on event triggered journeys and not for batch audience at this point in time. However, you could explore and test if the API reference used for 'sending multiple messages in single HTTP request' can mimic the batch evaluation and work for batch journey...

@Michael_Soprano  Yes, to rephrase that - If the user has opened the mail it would satisfy the email opened condition and it would go to the end path, if not then it would wait for the duration you have set to see if the reaction has happened in that duration, if no reaction on the email in the dura...

Hi @ButhpurKiran ,   One way to do this on a journey is to use a condition activity post the email activity using the collection management functions that would look into the interaction experience events and relate a click to its url and use it further in your journey. Collection management functio...

hi @Michael_Soprano ,   This is an incoming event timeout. This creates a second path for individuals who did not react within the defined duration. You can define an event timeout path between 40 seconds and 90 days.   Warm Regards, Reena John

hi @DiegoGa8 ,   Please refer to this documentation to enable the custom 'isSuppressed' field to be visible within your journey for use. Adobe Experience Platform data source | Adobe Journey Orchestration   Warm Regards, Reena John