sjuan.fajardo
Member
- Your Workflow URL
- https://connect.pabbly.com/v2/app/workflow/mapping/IjU3NjcwNTZjMDYzNTA0Mzc1MjZkNTUzMjUxMzEi_pc
- Consent to Access & Modify
- I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.
Hello!
Given this step's response:
We can say that if I were to create a filter based on this step's response and it would be true, the steps after should run, correct? For example:
BUT IT DOESN'T. It says "Condition is true" but all the steps after doesn't run. Let's call this filter #1.
If I use an already existing condition from a previous filter, called filter #0 (here is an example of a filter before filter #1):
AND I REPLACE FILTER #1's condition with ANYTHING from filter #0:
Basically, I'm using a condition that I know would 100% be true since it was a condition I needed to pass in filter #0 before getting to filter #1.
What's funny is that if I change it to this condition, ALL MY STEPS AFTER, they run. Even if both say "Condition is true".
I am using the same payload for both testing scenarios.
Given this step's response:
We can say that if I were to create a filter based on this step's response and it would be true, the steps after should run, correct? For example:
BUT IT DOESN'T. It says "Condition is true" but all the steps after doesn't run. Let's call this filter #1.
If I use an already existing condition from a previous filter, called filter #0 (here is an example of a filter before filter #1):
AND I REPLACE FILTER #1's condition with ANYTHING from filter #0:
Basically, I'm using a condition that I know would 100% be true since it was a condition I needed to pass in filter #0 before getting to filter #1.
What's funny is that if I change it to this condition, ALL MY STEPS AFTER, they run. Even if both say "Condition is true".
I am using the same payload for both testing scenarios.
