Cristi C.

In my case, I see such errors occasionally when the agent can't pick up a go-to route. If it happens often, you can check and improve the conditions, along with selecting a more intelligent model. If it happens rarely, it can be due to the context blowing up and confusing the AI about what to do next.

I did some testing with 'Handle in same task' and the outcome is what I wanted:

So, for me, I can get the expected outcome with 'Handle in same task'

It could be, but it forces the use of AI for something that generally didn't need it (implying use of credits and risk of error).

There are filters I've set in the 'Email Received'. Any reply coming via that loop won't benefit from that filtering.

And a second issue I just saw - if the setter doesn't run, then the getter fails. There is no 'null' behavior.

Speaking about variables, I have 2 blocks that, ideally, would set the same variable. Then, down the line, another block would read and use the variable value. The current problem is that, when trying to choose the variable to use, I'm forced to choose between setter 1 and setter 2 - they don't act like the variable is the same iinstance/reference. In other words, it seems that we can't have the same variable set from 2 different blocks. Did I get this right?