When you change the name of a start node input variable, the downstream nodes that map that variable are marked "Not Ready". However, the invalid mapping that uses the old name is not removed from the downstream node.

The steps below are an example of this behavior:

1. Create a treatment campaign with a string input variable named EMPL_STAT.
2. Add a multi-filter, process, or score node that uses a string input variable.
3. Map the input variable EMPL_STAT to the node created above.
4. Edit the start node properties and change the variable to EMPL_STATUS.
5. Review the mapping for the node created in step 2. Note that although it is marked "Not Ready", the mapping retains the old name.

Also, if you change the data type of an input variable, the downstream nodes are not marked as "Not Ready". However, the mapping is likely invalid after the change.

When the changed input variables are used in calculated items, nodes that use the calculated items display different behavior when the input variable is changed, depending on data type. When a date type input variable name is changed, the node is not marked invalid or "Not Ready". Instead, the node retains the old name and appears ready, although the campaign is unlikely to execute correctly. When a string type input variable name is changed, the node with the calculated item is marked "Not Ready".

Operating System and Release Information