@rajivkamathacc Take a look at this documentation on how to write back to journeyevents dataset. If the requirement is to validate that the message has been sent out for a profile or not and that requires a custom process then ingesting the feedback data via the flat file/API into AEP/AJO that uses ...

@Rohan_Aditya, Looks to me this is a batch segment. If it's a batch segment wait it will get evaluated on a 24 hr window. You can verify this from the segment overview screen when the last batch is completed and the next batch is scheduled. Look at some of the other recommendations from this thread....

@Hrya01 You can have a look at this data dictionary and dataset query examples. I believe, linkURL gets populated when you have the destination link added when you setup an offer.

@akwankl  One of the places where listObject is used on custom actions. Take a look at this documentation. To retrieve account object values have a look at the collection management functions

Is there a reason to keep this structure? You can remove this by going to the navigation tree in the email designer and removing it. Also, the advanced expression that checks stateCode='QB' you mentioned can't be used in dynamic conditions. <% if(context.profile.location.stateCode === 'QB') { %>  ...

@JESUSBA1 Looks like you're using Adobe campaign classic. Moving this post to the ACC community. Meanwhile, refer to this post.

@krishnan5 Refer to this documentation on other ways to create test profiles along with the file upload method.

@saicilia Looks like you're using a custom action (WritebacktoAEP) with a payload that contains an expression of a prior custom action mentioned and it throws an error about that. Fixing the payload that's part of the WrtiebacktoAEP custom action might fix this issue.

@Skotmor Can you share the screenshot and condition?

Looks like this is related to the workfront. Take a look at this documentation. Moving this question to workfront community.