This behavior is documented in the experience league page https://experienceleague.adobe.com/en/docs/journey-optimizer/using/whats-new/previous-rn-new/release-notes-2024 and is expected. 

CSV file audiences can be leveraged in journeys and campaigns. https://experienceleague.adobe.com/en/docs/journey-optimizer/using/whats-new/previous-rn-new/release-notes-2024  

Test profile will be only used to display the personalization data in the message sent to the seed addresses. 

You can add an additional filter based on nodeId and the Id can be retrieved by clicking on the end node. SELECT to_json(_experience), timestamp FROM journey_step_events WHERE _experience.journeyorchestration.stepevents.journeyVersionID = <journeyVersionId> and _experience.journeyOrchestration.ste...

I don't think it is feasible - can you share more details on your use case ?

That's right. If another ingestion flow is actively writing to the same dataset/fields around the same time that a Journey updates them, the final field value may reflect the most recent ingestion rather than the Journey update. It is recommended to configure a dedicated dataset (with required attri...

You can take a look at the following documentation links which details the steps on how to send profile attributes and audience membership data to Pega Customer Decision Hub for next-best-action decisioning.https://experienceleague.adobe.com/en/docs/experience-platform/destinations/catalog/personali...

Looks like vacationPacakageDetails.fullDueDate is on the experience event schema ? Accessing experience event attributes via #{ExperiencePlatform.ProfileFieldGroup.timeSeriesEvents._xxxx.vacationPacakageDetails.fullDueDate} will not work (if you are using this in a batch journey starting with a read...

right, it is a direct UPS update and won't be available in "AJO Push Profile Dataset". You can query the profile snapshot dataset to fetch the push token details.https://experienceleague.adobe.com/en/docs/journey-optimizer/using/channels/push/push-config/push-gs

There wouldn't be duplicates as only single instance of a profile can be in a journey at a given point of time and hence, it will be an union