Error with filter component
I modified some connections in a flow that I had already created, but I did not publish it. After a while, I realized that there was a problem that prevented the entire flow. After debugging, I discovered that the problem was the filter component that was not filtering. What I did to solve it was to recreate exactly the same decisions that existed in this filter and it worked again.
I don't have any examples because it was literally the exact creation of the same component, with the same decisions
Is this expected behavior? Has anyone experienced this?
I'm using the 3.2.0 version
1 Reply
Not sure to understand this, you are saying the condition block did not work, you re-created it and it worked again?