Hi @Bryce, I am sorry for the trouble. I suspect this comes down to n8n failing to render such values even if just one expression cannot be resolved (for example because it references data from a node that hasn’t run yet) as described here:
The product and engineering teams are aware of this issue, but unfortunately I do not have an ETA for a fix yet. You might want to follow the original thread on this for any updates.