the tasks are showing the non-true route function as an error!

[charles.araruna]

Since yesterday the tasks are showing the non-true route function as an error! this is not an error.
And it is disturbing the reading of the logs.

 

[shahidul islam pranto]

The error message will appear when the condition turns out to be false.

On the other hand, a success message will appear when the condition turns out to be true.

Do not worry about the error message, but make sure that your condition is right.

 

[charles.araruna]

Yes I understood.
But this change is making it difficult because now all the logs have tasks with an error and so I can't understand and treat what an error really is.

 

[shahidul islam pranto]

Just follow the marked message. Ignore the error for this filter condition.

 

[charles.araruna]

I understood what you said, but I believe you did not understand what this change is causing as a problem.

with this change the log of all executions are appearing as an error.
How will I identify a real error?
will I have to go into every execution and evaluate every step? this is not feasible.

 

[shahidul islam pranto]

Yes, I understand now. Maybe you would request the feature in the pabbly feature request to make a non true filter a success, not an error, so that it can be easy to distinguish the real error.

 

[ArshilAhmad]

Hey @charles.araruna,

I have noted your concern. Please allow me some time to look into this issue. I will get back to you as soon as possible.

 

[charles.araruna]

Yes, I understand now. Maybe you would request the feature in the pabbly feature request to make a non true filter a success, not an error, so that it can be easy to distinguish the real error.

but that was how it was... it changed yesterday.

 

[charles.araruna]

Hey @charles.araruna,

I have noted your concern. Please allow me some time to look into this issue. I will get back to you as soon as possible.

ok. tks

 

[StephenStowell]

I understood what you said, but I believe you did not understand what this change is causing as a problem.

with this change the log of all executions are appearing as an error.
How will I identify a real error?
will I have to go into every execution and evaluate every step? this is not feasible.

Agreed woke up to thinking Pabbly as broken this Morning.

 

[ArshilAhmad]

We have fixed this issue. 'Condition is False' will no longer give a Partial Failed status. Apologies for the inconvenience caused.