@ChesterBe  In Handlebars, the values returned by the {{expression}} are HTML-escaped. If the expression contains &, then the returned HTML-escaped output is generated as &. If you do not want Handlebars to escape a value, use the “triple-stash”. https://experienceleague.adobe.com/en/docs/journ...

If this is in the message personalization editor, following function can be used https://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/personalization/functions/dates#week-of-year  {%= weekOfYear(datetime) %}   If it is in advanced expression of condition nodes/waits/...

I see you are forming a stringified JSON and updating it on profile. Can you query the step events and see what is the http error code on the action node ?  https://experienceleague.adobe.com/en/docs/journeys/using/building-journeys/sharing-journey-steps/query-examples#message-action-errors 

Could you share the screenshot of the journey with the details of the branching ? 

Events ingested in batch or events from internal Journey Optimizer datasets (Message Feedback, Email Tracking, etc.) cannot be used to trigger a journey.    https://experienceleague.adobe.com/en/docs/journey-optimizer/using/configure-journeys/events-journeys/about-events 

If the customer data is loaded in dev sandboxes and if the channel configuration is created, yes - that is very much likely. As a best practice, allowed list can be enabled. https://experienceleague.adobe.com/en/docs/journey-optimizer/using/configuration/monitor-reputation/allow-list     

Kindly check if the count of profiles that were successfully sent to the API service are matching with what you see downstream (by querying step events dataset) to isolate the issue further. https://experienceleague.adobe.com/en/docs/journeys/using/building-journeys/sharing-journey-steps/query-examp...

Use it on the following lines as mentioned previously as traject is an array object and it needs to be iterated over. eventId needs to have backticks. Example {{#each context.journey.events.`eventId`._tenant.npoEvent.traject as |s|}} {%= replaceAll(s.discountedPrice,"([0-9]+\\.[0-9]{2}).*",...

It's a different error now and the function signature is not being matched. You are using an array object where as the function expects a string. You can validate it on the following lines Example {{#each context.journey.events.`eventId`._tenant.npoEvent.traject as |s|}} {%= replaceAll(s.di...

Take a look at this note on how profile estimates are generated. https://experienceleague.adobe.com/en/docs/experience-platform/segmentation/api/previews-and-estimat...    Profiles will qualify against the segment based on how it is configured. If it is a batch segment (it needs to wait for the batc...