As this is a simple batch journey (with a single channel) which does not need any further orchestration, you can very well configure it in campaign.

You can leverage datasetLookup helper which is currently in Beta https://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/personalization/lookup-aep-data for your case

looks like the response is an array object, you can access it on the following lines{{#each context.journey.actions.<actionId>.data as |res|}} {{res.revised_prompt}} <br/> {{res.url}} {{/each}} 

Kindly check if you have "view profiles" permission and if the default merge policy is selected. There also must be an estimate to view profiles.https://experienceleague.adobe.com/en/docs/experience-platform/segmentation/ui/segment-builder#segment-propertiesAlso, you can double check by navigating t...

Did you check if you have the permissions mapped to the role, that you are part of ? https://experienceleague.adobe.com/en/docs/journey-optimizer/using/push/push-config/push-configuration#setup-permissions 

Are you using any contextual attributes in the fragment content ?  https://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/fragments/save-fragments

Can you share how the response attributes are being accessed in the email message ?

kindly log a support ticket for this issue.

You can validate it on the following lines {%let a = now %} {%let b = toDateTimeOnly("2024-12-19T09:57:27.980Z") %} {%let c = dateDiff(b,a) %} {%#if c =0 %} // If the difference is zero, product field date is today render_1 {%else%} default_render {%/if%}

Since the SMS content includes a URL, its preset should also have a defined subdomain for shortening the URL, which appears to be missing. Reference - https://experienceleague.adobe.com/en/docs/journey-optimizer/using/channels/sms/create-sms