Troubleshoot a Flow Referencing a Deleted Resource

When a flow depends on something that no longer exists, you’ll typically see:

• A node/action title highlighted in red
• A warning message when you open the node
• A Flow Issues tab appearing on the right side of the editor

[CAPTURE: Flow editor showing a node title in red, indicating a missing dependency.]

A missing dependency happens when a flow references something that is no longer available, for example:

• A deleted contact field referenced like @fields.age
• A deleted contact group used in a split or group action
• A removed channel referenced in a send or routing action
• Any other workspace resource your flow depends on

1. Click the red node in the flow editor.
2. Open its configuration panel.
3. Look for an error message such as:
   • “Cannot find a field for @fields.<field_name>”

[CAPTURE: Node edit panel showing an error message like “Cannot find a field for @fields.whatever_field_name”.]

1. In the flow editor, look for the Flow Issues tab (red) on the right side.
2. Click Flow Issues to open the list.
3. Review all missing dependencies in the panel.
4. Click each issue to jump directly to the affected node.

[CAPTURE: Right-side panel showing a red “Flow Issues” tab, expanded to show a list of issues.]

Scenario A: Missing contact field

Problem: The flow references a field like @fields.age, but the field was deleted.

Fixes:

1. Option 1 — Recreate the field: Recreate the contact field with the same name/key (recommended if many flows use it).
2. Option 2 — Update the flow to use an existing field: Edit the node and replace the missing variable with the correct field.
3. Option 3 — Remove the reference: If the value is no longer needed, remove it from the message, expression, or update action.

[CAPTURE: Contact fields management screen showing a field being recreated, OR a flow node being edited to replace @fields.age.]

Scenario B: Missing contact group

Problem: A group used in “Add to Group”, “Remove from Group”, or a group-based split no longer exists.

Fixes:

1. Recreate the missing group, or
2. Edit the flow to use another existing group, or
3. Remove the group action if it is no longer relevant.

[CAPTURE: Group selection dropdown in a node showing a missing group replaced with an existing group.]

Scenario C: Missing or changed channel

Problem: The flow references a channel that was removed or replaced.

Fixes:

1. Confirm the workspace still has the needed channel connected.
2. Update the flow configuration to use a valid channel or channel-agnostic sending behavior (based on your workspace setup).
3. Re-test message sending with the simulator and (if possible) a real channel test.

[CAPTURE: Workspace channels list showing active channels and a flow node referencing a valid sending option.]

Scenario D: Missing variable or invalid expression

Problem: An expression references something that no longer resolves (field, result, or context variable).

Fixes:

1. Identify the missing token in the expression (examples: @fields.*, @results.*).
2. Replace it with the correct variable or remove the logic.
3. Use the simulator action log to confirm values are set as expected.

[CAPTURE: Expression editor showing a missing variable being replaced with a valid one.]

1. Reopen Flow Issues to confirm the list is cleared (or reduced).
2. Run the flow in the simulator.
3. Check:
   • Message rendering (no missing blanks)
   • Contact updates (fields/groups updated correctly)
   • Split routing works as expected

[CAPTURE: Simulator panel showing a test run and the action log confirming updates.]