Skip to main content
Discovery

Dynamic JO Initial Setup Needs Work (stop auto sync, edit source name)

Related products:CS Journey Orchestrator, Email & Notifications
  • August 22, 2025
  • 3 replies
  • 37 views

dayn.johnson
Forum|alt.badge.img+7

I’ve started building out programs in Dynamic JO recently, and have run into some annoyances.

Issues

  1. Audience auto-syncs with single uniqueness criteria
  2. Can’t edit source name once added

Details

  1. Once you add a new source, it immediately starts syncing – you have to wait for it to complete the auto sync before you can update your advanced settings (Uniqueness Criteria, Mandatory Fields, anything else). It also tends to automatically pick an email address (sometimes) for the recipient, and when it looks to send to the CSM email for an external JO, I’m a bit confused. This forced delay makes me end up having to task-switch, which leads to inefficiencies in my workflow.
  2. If we’re cloning a JO (ex: testing), it seems like we have to jump through hoops to get the source name to not say “TEST_Lorem Ipsum Program name” – which doesn’t look great when we’re trying to build our programs and keep JO names clean.

The ask

Could someone explain the logic for autosyncing the audience and locking the source names? This all feels like it was easily achievable in Advanced JO, which makes it all even MORE frustrating. I’m liking the wins in Dynamic JO (particularly the ability to have an evaluate step with multiple branches before an email step), but there’s so much I miss from advanced JO.

Audience View

 

3 replies

vmallya
  • Gainsight Employee ⭐️
  • September 9, 2025
New IdeaDiscovery

vmallya
  • Gainsight Employee ⭐️
  • September 9, 2025
  1. we are working on limiting the auto-sync and make it manual 
  2. the query names as derived from the program name, currently

dayn.johnson
Forum|alt.badge.img+7
  • Author
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • September 9, 2025
  1. we are working on limiting the auto-sync and make it manual 
  2. the query names as derived from the program name, currently

@vmallya – awesome news!

re: 2 – would making the audience sync manual allow us to change the query name if the audience hadn’t been synced? Just musing here, but feels like that’s locked in once it syncs, so in theory if the sync doesn’t happen until we explicitly request it, we should be able to circumvent that in case we need to change the program name after initially cloning it.