Now Assist AI Agents Version Mismatch Between Dev and Test
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Community,
Looking for guidance/best practices around Store app version mismatches across ServiceNow environments.
We have a scenario where a Now Assist-related Store application is on different versions between dev and test environments. The higher environment is already on a newer major/minor version, while dev is still on an older version.
My concern is:
If we upgrade the app in dev to match test, could it change the behavior of existing AI agent capabilities/workflows?
For example, behaviors related to generated plans, orchestration, prompts, or skill execution.
If behavior changes in dev after the upgrade, how do teams safely validate and avoid issues when promoting future customizations to higher environments?
Would like to understand:
Recommended approach for handling Store app version alignment across environments
How teams test AI Agent/Now Assist behavioral changes after upgrades
Whether app version mismatches themselves are a bigger risk than upgrading
Best rollback or mitigation strategies if AI behavior changes unexpectedly
Any real-world experience or best practices would be appreciated.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Also, one additional challenge in our case is that the test environment is read-only from our side, so we do not have direct control over the Store app versions there.
Since test is already on the newer Now Assist AI Agents version while dev is still behind, I wanted to better understand the safest way to handle the version alignment and deployment/testing implications before proceeding with the upgrade in dev.