Filter Stopped Working

(Vladislav Arbatov) #1

Hi.

So I have this flow that worked perfectly. One action way triggered when there was an empty reply from external API (Data is empty). I changed nothing and somehow the pipeline broke. Now when Flow receives an empty reply from an API (Data: [], Body: []) in tries to trigger this action despite of the filter (which clearly states: do not trigger if empty!) and all that clearly throws an error (Message can't be blank).

I’m trying to figure it out if it’s me or if you changed something?

(John Jackson) #2

The error message Message can't be blank is new (last few days) so I think maybe this is what’s caused the behaviour to change, or to at least be noticed.

Assuming this is what’s happened, then prior to this you were sending a blank message, which wouldn’t have done anything, but wouldn’t have caused an error either.

In that case also, I guess maybe your filter wasn’t working before?

If data contains [], then this wouldn’t be considered empty, as the data consists of a single empty array. You could instead use a filter on the Body field to say if Body equals [].

Hope that helps you move forward with this!