New Dynamic JO Should Have Multiple Queries (just like older advanced JO)

@vijay visibility on this

This is a feature regression compared to the old advanced JO, echoing the sentiment from other admins cloning JOs to achieve different segmentation is additional assets that shouldn’t be required.  Additionally, as Gainsight looks forward, how would it anticipate to migrate JOs to the redesigned JO where old programs utilize multiple queries and the new JO doesn’t support this functionality?

Woooahh, @Stuart with the insightful question I hadn’t yet considered! Would love to hear the answer.

​@vmallya – thought of a potential workaround (at least for regional queries). Is there any update on how multiple queries will be handled in dynamic JO (and how our existing JOs might be migrated)?

Thank you for the detailed scenarios on this thread. Sharing a consolidated update on how each of the multi-query use cases can be handled in the new version of JO.

Regional and timezone-aware sending (​@dayn.johnson , ​@sarahmiracle , ​@heather_hansen )  — in February 2024, we introduced the Action Execution Schedule feature in the new version of JO, which lets a program send at the local time of each recipient by reading a timezone field maintained on the participant, contact, or account record. This is designed to replace the need for separate region-specific queries. We understand the concern we have heard from some customers that this timezone attribute is not currently maintained in their data, which blocks adoption of the feature. We do not believe adding multiple queries is the right/accurate solution for timezone-based sending; the scalable path is a single program driven by a maintained timezone field. We would encourage teams to populate this attribute at the participant, contact, or account level so the Action Execution Schedule can deliver the per-timezone behavior this thread is asking for.

Audience segmentation inside a single program ​(@heather_hansen , ​@dayn.johnson ) — for conditional routing such as CSM/AM fallback, primary/secondary contact logic, or standard vs. premium tiers, the recommended pattern is to either use case statements in the query to derive the segmenting attribute - (we also extended case statements to support email data type), or use the Evaluate step to branch participants down different paths with distinct email configurations. Either approach achieves the same segmentation outcome within one program without requiring multiple queries.

On multiple daily executions, with the April 2026 release, the new version of JO supports participant sync multiple times per day, so programs can re-evaluate and enroll new participants at a higher cadence than the prior once-daily run.

Routing to both Primary and Secondary contacts from a single program ​(@mobrien14 ) — we believe this use case does not require multiple queries. A single query can UNION the Primary and Secondary contact email fields from the Account/Company record, producing two participant rows per account (one for each contact), which a single program can then enroll and email. If the contacts are modeled as separate Contact records with a role field, the same outcome is achieved with a single query and a role-based filter. Happy to walk through the query setup to validate this pattern.

Per-segment sender mapping (​@sarahmiracle )— this can be handled within a single program using two supported patterns: (1) an Evaluate step with per-branch sender configuration, branching participants by region, tier, or account owner and configuring each branch's email step with its own sender; or (2) email variants with local header configuration, where a single email step holds multiple variants, each configured with its own sender, and the variant is selected per participant using the same conditional logic. Either approach delivers the segment-specific "From" behavior that multiple queries previously enabled.

Workaround pain and staying on legacy Advanced Programs ​(@sarahmiracle , ​@romihache , ​@dayn.johnson )  — with the capabilities above (Action Execution Schedule, case statements, Evaluate branching, UNION support for multi-recipient queries, per-branch or variant-level sender configuration, and multiple daily participant syncs in the April 2026 release), the scenarios originally covered by multiple queries can now be handled within a single program. Teams should no longer need to maintain parallel programs or maintain multiple queries as source to achieve this behavior.

Migration from Advanced JO programs that rely on multiple queries (​@Stuart , ​@dayn.johnson )— ideally, with the patterns outlined above, a new single query can be authored directly in the new version of JO to cover the original multi-query scenario. For teams who would prefer to carry forward their existing query logic, we are solutioning an option to migrate selected queries into the new version. Further details on the migration path will be shared as the scope is finalized.

Please continue to share any gaps you encounter against these patterns, and we will keep this thread updated.

​@vmallya thank you for this update.  I have provided feedback via the Product Council that I do not believe is covered in these new workflows.  Are you also considering the Product Council feedback, or should I also document here?

Yea, I like the update would would have appreciated acknowledgement of the continued gaps we already brought up with you in product council, rather than making it seem like this issue is resolved. We got a lot of great individual features, that are slowly replacing one functionality (while adding some additional capability along the way).

​@angela_domenichelli and ​@bradley, your Product Council feedback is very much on our radar and shaping where we take this next. We are coordinating a working session with the Product Council in the next 2 weeks to go through it together and make sure the remaining gaps are fully understood.

I have intentionally kept this thread open rather than marking it Released, because we do not consider this resolved until we have worked through your input with you. 

Great to hear, thank you!