Best Of

Hi @Zeb Loewenstein

I've thought of a way to bypass this error, and allow you to have one Parent workflow with all the Child Workflow Modules below it.

In each of your Child Workflows, add the "Get Sheet" and "Array Management: Extract Field from Array" modules to get all the Column Names in the sheet before looping through to add the new column if there's a multi-select match.

This way you can add in a CONTAINS Junction to see if the array of column names in this sheet contains the name of the new column already:

If there's a column already in the sheet with that person's name, the child workflow will have a successful result (result of nothing) which will prevent it from ending in an error.

I've added in two fail states just so they appear in my run log and I can keep track of how the workflow is going through each module.

Here are the pieces broken down:

Get Sheet

Copy the Data Reference to the Columns array.

Array Management: Extract Field from Array

Uses the Column Array reference to grab the title key.

Get the data reference to this new array of ONLY the column titles.

CONTAINS Junction

Look through the new Column Array as the Values to search, and use the runtime.entities.Name that was pulled from your Parent workflow to check if that name exists as a Content in the Array (or whatever you're using as the new column name).

The SUCCESS state (the column name already exists in the array) is just a plain state with a title for my run log. This will cause the workflow to end in SUCCESS but to take no action.

The FAIL state (no column exists) is the MATCH junction that we already had set up, where if there is no column and if the value (e.g. "AZ") exists in the multi-select array, it adds the column. Otherwise, even if the column does not exist, if there is no matching multi-select value it does nothing.

Let me know if this makes sense and will work for you.

Cheers,

Genevieve