Hi Adrian,
I am able to reproduce your issue. I have opened a bug report with engineering to look into it. In the meantime, there is a workaround for this. Rather than use the templating context, you can use inline variables. First, delete you email action so you don’t get the error anymore. Then, create a new email action and use inline variables in your email body. For example:
