Skip to main content

Why can’t I save the scenario after adding a content source to the action nodes?

Updated

Use this guide if you can't save a scenario after adding or editing a content source in an action node.

Symptoms

An alias conflict may be causing the issue if:

  • The scenario doesn't save after you add or edit a content source.
  • You see an error such as Alias 'tblsrc1' is used in multiple nodes for different content sources.
  • A message or webhook fails with an error such as ContentSourcesAccessor object has no attribute ....

Cause

An alias conflict occurs when the same alias points to different content sources within one scenario.

This can happen when:

  • Two nodes use the same alias for different sheets or tabs.
  • Content sources are listed in different tabs within the same Google Sheet. Each tab is treated as a separate content source.
  • A node or template was copied and retained an outdated alias reference.

Resolve the conflict

  1. Open the content source settings in each affected node.
  2. Check which sheet or tab each alias references.
  3. Give each content source a unique alias.
  4. Update all personalization tags and Jinja references to use the correct alias. Check copied blocks and templates as well.
  5. Save the node, then save the scenario again.

Example

If two nodes use different tabs, don't use tblsrc1 for both sources. Assign a unique alias to each source, such as:

  • tblsrc2
  • tblsrc3

Then update the related personalization tags and Jinja references to match the new aliases.

When to contact support

Contact support if the scenario still doesn't save after you align the aliases and references.

Include the following information:

  • The scenario URL
  • The complete error message, if visible
  • Screenshots of the affected node settings
  • A HAR file from the session

Summary

A scenario may fail to save when different action nodes use the same alias for different content sources. Assign a unique alias to each source, then update all related personalization tags, Jinja references, copied blocks, and templates before saving the node and scenario again.

If the issue continues, contact support with the information mentioned above.