Can you try it on the following lines {% let a = context.journey.events.`815461771`.commerce.order.cancelDate %}{%= formatDate(toDateTimeOnly(a), "EEEE, LLLL dd, YYYY") %}

well, it's not explicitly populated in the path "personalEmail.address". Your screenshot indicates, its only part of the identityMap and you may want to review the source from where the profiles are being created.

Can you check if "personalEmail.address" attribute is populated in the attribute sections of the profile ?

Kindly take a look at this note in the documentation https://experienceleague.adobe.com/en/docs/journey-optimizer/using/offer-decisioning/managing-offers-in-the-offer-library/configure-offers/add-constraints#frequency-capping  

Each helper https://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/personalization/functions/helpers#each can be leveraged here to iterate over multiple accounts and if you give a condition to select only those accounts where balance = 0, it will return you both. You c...

It is only one test profile that can be specified in test mode, in the current state. However, If you need multiple branches of the journey to be validated, you can create an audience of test profiles with different data points per the conditions configured and publish the journey live. Results can ...

Custom experience event schemas can be selected too in the drop down. In fact, the ones starting with GMF and Test in your screenshot are custom ones.

Take a look at this note.https://experienceleague.adobe.com/en/docs/journey-optimizer/using/get-started/guardrails Agreed, it is visible but cannot be used. Feel free to log a client care ticket on this.

Sanity journeys can be created with the read audience + end activity and once this is published, you will have the profiles that entered the journey (as a result of being qualified into the audience) in step events dataset. These profiles can then be verified (either by profile lookup or by writing ...

Here is an example {% let d=now %}{%= formatDate(d, "EEEE, LLLL dd, YYYY") %}