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.

You don't need it until you do, then, it is too late haha. I guess you have also encountered the profile richness license usage guardrail, at least that was the first time I wish I had this function.  Really helpful idea, you have all my support. 

Descripción - Me and my colleagues are using the set auto_to_json function a ton while querying, partially it is because it only works for a single session. Therefor, one day, I thought that it would be a low effort hight reward implementation inside the query service UI.  This function might be imp...

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