Hi, @Pradeep-Jaiswal ,  I think this is what you are looking for:  Just drag the attributeA twice inside an event and change the "all" for "any". This way you will be registering all the events you need.

Ok, we solved it. The problem was the timeout, we raised it to 90 seconds, and the repeated entry of profiles timeout, we lowered it to the minimum. 

As I mentioned, above, It is not JSON, it is string in form of a JSON.

Of course, here they are:The journey: And the "recibo pendiente" code:if ( isEmpty(#{ExperiencePlatform.fieldgroup1.profile._clienttechsa.customPersonalization}) ) then ( concat ( concat ( concat ( concat( concat( ...

I have created a Journey that updates the profile in the DEV sandbox.When in test mode, everything works fine. But then, when Published, the path that the journey takes is sometimes the correct one and other times the alternative error/timeout one. I am doing the same tests in test mode as when Publ...

Not yet

Yes, we do have it enable along with Edge segmentation.

Yes, they are, the last screenshot I sent are from the Profile Endpoint: https://platform.adobe.io/data/core/ups/access/entities

This is the exact problem, with this call, I am getting this response for this call: No profile attributes. As I show in the screenshot above, this profile does have attributes but I am unable to see them. We exported first name and custom_personalization attributes to the Custom personalization wit...

Thank you, @maggod You are totally right. I tried the interaction API call and I got this response: I was expecting the segmentMembership and the attributes, but I can't see those. Did I forget to toggle anything? Any idea of what could be possible happening?