Fixing Missing Dependencies

In certain situations, you may discover that a flow relies on an element which no longer exists. When this occurs, the action title will appear in red (as illustrated above) to indicate the presence of an issue within the flow. For instance, you might encounter a flow that references a contact field through an expression such as @fields.age, even though the corresponding ‘Age’ contact field has been deleted at some point.

When this happens, your flow will continue to operate, though it may produce unexpected outcomes. In some scenarios, such as attempting to update a contact field that is missing, no action will be taken (apart from the field not being set).

In other cases, the impact might be more apparent. Consider a Send Message action structured like the following example. Here, the omission of the value for @fields.volunteer_id could potentially cause confusion.

Upon creating a node with a missing dependency, the node itself will turn red. If you click to edit the node, a notification will appear stating: ‘Cannot find a field for @fields.whatever_field_name‘.

Additionally, a new red tab labeled ‘Flow Issues’ will appear on the right side of the editor.

Select the ‘Flow Issues’ tab to view a comprehensive list of all missing dependencies. Clicking on any entry will direct you to the specific node within your flow.

Note that contact fields are not the only elements whose absence can trigger dependency errors. Similar issues may arise from deleted contact groups, deactivated channels, or various other referenced components within your flow.