So the problem is that the Log action doesn’t support unstructured metafields at this time.
I can just instruct merchants to add custom definitions, but if unstructured metafields aren’t supported then they shouldn’t be shown as an option in the action.
Hey @Dylan - just following up here, as we’ve recently pushed a fix that should resolve this issue. Can you let me know if you’re still seeing metafield variable access issues when replicating the set up above? If so, just ping me here and I can take a look for sure - hope this helps!