Task Error on null input - would prefer ignore

[Dylan Halliday]

So I have a workflow that uses regex to remove the square brackets and quotes before processing it. E.g. ["string"] becomes string.
The issue is, this field is not always filled so it might be null. I want to only run the task when the input != null.
The rest of the task runs fine. So overall, there is no issue. However, it gives me an error email. It's not an error.
This workflow iterates over an array of objects, is there any way to have logic that skips the task on null but the rest of the tasks on that iteration continue?
My understanding on the filter action is, it skips the rest of the tasks for that iteration. Is that right?

 

[ArshilAhmad]

Hi @Dylan Halliday,

You need to add a Router to your workflow after the Iterator step. Add all the steps to Route 1, including the Regex step, and set the filter condition to execute when the field IS NOT EMPTY. In Route 2, add all the steps excluding the Regex step, and set the filter condition to execute when the field IS EMPTY.

 

[Dylan Halliday]

Ok thanks. I was hoping this wasn’t the answer. It means having to maintain two lots of tasks when fixing bugs etc.
Also the UI to copy and paste from one route to another is not efficient.

I’ll leave it for now and hopefully a pabbly connect UI which I saw concepts of is in the works

 

[Dylan Halliday]

A route that can then continue back to a single path after splitting would be amazing

 

[ArshilAhmad]

A UI change is indeed in the works. The feature you are looking for will be available very soon!