Now Assist AI Agents Version Mismatch Between Dev and Test

[Sahithi K]

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!

[Dr Atul G- LNG]

Hi @Sahithi K 

When we upgrade and log in, the plugin fetches and updates the latest files and fixes for that particular module. If there are no changes in a few files, they may not be impacted by the plugin update.

In your case, you need to read the plugin release notes to understand what is included in the latest version. It is also recommended to keep all instances on the same plugin version to avoid issues like the one you are facing.