I am seeing something similar and in my case , filter is working as expected from “Event Trigger” configuration but when I tried to use same filter in workflows under event filtering it says not valid.
Hi Chirag,
I applied the same json path to one of my workflows and it saved successfully.
Have you tried deleting the trigger and adding the filter back? Also, did you copy/paste that filter from another text editor? Sometimes the character encodings from different editors can cause issues.
The filter was fine. I noticed below behaviour from my testing:
- filter works fine under “Event Trigger” test option, which you try to do from subscription section.
- Filter is not working when you are testing workflows from “Test Workflow” section. It will go beyond first step even if the conditions do not match.
- Real time workflow executions are getting filtered as expected.
I created 2 different workflows to test this behaviour.
The “Test Workflow” feature doesn’t factor in the trigger filter. What actually happens is Workflows simulates an ETS event using the provided sample data, and it will always trigger the test regardless of the filter, since it’s not an actual ETS event. This is why a live run of your workflow honors the filter, because it’s being triggered by actual ETS events.
The Workflow team is aware of this and has a feature in the backlog to simulate the trigger filter in “Test Workflow”.
1 Like