Issues with step returning a failed where it should return a succes

[apps]

Hi,
I have this flow where Fetch a Partner from Partnero fails if it cannot find a partner. This causes all following steps to fail instead of run.

I want one route to run if it returns Not found and another route to run if it returns a partner.

But I can't because Pabbly Connect returns a fail on this. I already tried to make a lookup table as a workaround hoping this would solve it but with no luck. A solution would be for the action to just return a succes with "Partner not found" - because then the flow could continue.

How can I solve this?

Flow URL: https://connect.pabbly.com/workflow/mapping/IjU3NjUwNTZlMDYzZjA0MzU1MjY5NTUzNTUxM2Ii_pc

 

[ArshilAhmad]

Hi @apps,

Please try setting up the filter conditions for your routes in this manner. This should help you with the issue you are encountering.

 

[apps]

@ArshilAhmad Thanks, however it seems you're misunderstanding the source of the problem and my message. The problem is not the matching of the router filters but the fact that the Fetch partner step returns an error when no partners are found. So this stops all following steps. It should return Success when nothing is found still and not an error because if not all following steps seem to stop. So no change of the router filters will do anything about this because the behaviour of Pabbly seems to be to stop all following steps that build on steps that error. I have tested your solution still - please check the flow again.

Here is a failed task ID after those changes still: https://connect.pabbly.com/task/history

 

[Supreme]

Please allow us some time, we are checking on it.

 

[ArshilAhmad]

@ArshilAhmad Thanks, however it seems you're misunderstanding the source of the problem and my message. The problem is not the matching of the router filters but the fact that the Fetch partner step returns an error when no partners are found. So this stops all following steps. It should return Success when nothing is found still and not an error because if not all following steps seem to stop. So no change of the router filters will do anything about this because the behaviour of Pabbly seems to be to stop all following steps that build on steps that error. I have tested your solution still - please check the flow again.

Please enable the 'Ignore Error' feature in step 19 of your workflow and see if that fixes your issue. Doing this shall allow the routes to execute.

 

[apps]

Thanks, but it still seems to show up as a failed tasks even after enabling this though the flow continues, which is not true. Nothing should fail here. Simply if no Partner is found it should create a new partner and not show up as a failed task at all. The Fetch a Partner action should be green because there is no error. There just isn't any partner which is exactly what it should find out.
It's an issue that the flow shows up as a false fail.

 

[apps]

I have these fake errors filling out my tasks runs constantly for every lead that signs up which makes it impossible to know what is actually an error. This is not working :-(

 

[Supreme]

Hey @apps

Because the Partnero API does not provide a response code after successful completion, the workflow mistakenly regards it as a failed task.

Therefore, it is necessary to reach out to the Partnero support team to request the inclusion of a success status in the search action step.

 

[apps]

@Supreme Ok thanks, I have written them now.