The expression no longer works for me in 1.94.1:

Questions
1

The expressions inside the fields of the nodes of n8n version 1.94.1 no longer work correctly. I had to return to a previous version like 1.91.0 but everything still works fine for me.

For example, this expression no longer works for me in 1.94.1: “{{ !$(‘Telegram Trigger’).item.json.message.text.startsWith(‘/’) ? $json.memories.toJsonString() : “” }}”.

Apparently after the node name it recognizes item “node.item.???” but, then nothing else so it does the incorrect expression giving me problems with my workflow.

Information on your n8n setup

  • n8n version: 1.94.1
  • Database (default: SQLite): Postgres:17.2
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • **Operating system: Ubuntu server 24.04 **
2

Hey @Aris_Montero ,

I ran into the same issue you’re facing with expressions few months back. It seems that sometimes using item.json don’t works reliably in some cases.

Try updating your expression to use first().json instead. Here’s what worked for me:

{{ !$('Telegram Trigger').first().json.message.text.startsWith('/') ? $json.memories.toJsonString() : "" }}

Switching from item.json to first().json resolved the issue in my workflow. Hopefully, this works for you too!

3

Hi Sudhanshu, thanks for the tip. It may have worked for one workflow, but not for another. So if I use my own n8n server, I’d better stick with a version where all my workflows work.

I assume this will be fixed someday, since there have been like 3 new versions and nothing, everything remains the same. I’ll stick with 1.91.0 for now, as everything works great for me.

I understand that the first().json option works fine for me if it’s the first item, but if there are more, it won’t work. There’s another case that I don’t know how to explain right now, but I think it needs to be fixed or they give us an option to achieve what was already possible.

I like expressions because it saves a lot of work and also greatly reduces the logical part of the conditions to resolve.

Thanks again for responding to my post…

1 Like
4

You’re welcome! @Aris_Montero
Glad to hear 1.91.0 is working well for you, and hopefully the issue gets addressed in future updates.
Keep me posted if you figure out the other case!

Also feel free to mark that other message as solution, so that it will be helpful for others too.

Happy building!