Skip to main content
  • Home
  • Ideas
  • Prevent query from syncing right after program cloning

Prevent query from syncing right after program cloning

Related products: CS Journey Orchestrator, Email & Notifications

Hi there

When one clones a program (dynamic), with a query, the query starts to sync upon cloning without letting us adjust said query (which seems a logical sequence of action to edit the query after cloning) or do anything else, really. 

It is a waste of time to trigger the sync of a query we haven’t yet modified or we haven’t yet modified the program. The reason for cloning is often that a change needs making (to regionalize, to adjust, to make up for the fact we cannot edit a live program). 

There is no need to sync the query right after cloning. 

I would request that the query doesn’t sync on its own until we have gone in and clicked on “save & sync” OR on “Sync All”.

Thanks

A

Please, for the love of God make this happen. The number of times I’ve had to just sit and wait for the sync to finish before I could start working on the cloned program is mind boggling. 

Glad to see I’m not alone @saltamash 🤝

Additional request: when we build the query from scratch, we should have two options: 

  1. Save & sync, as is currently
  2. Save only: this is required because when we build the query, we haven’t yet configured the uniqueness criteria and other settings which will impact who syncs and who doesn’t. As such, having the query automatically sync when we are all done with the additional config which happens outside the query.

Thanks!

A

Terms & ConditionsCookie settings