Need feedback on 26.6 upgrade

RE: Need feedback on 26.6 upgrade

Mike Schmitt — Wed, 15 Jul 2026 13:58:36 GMT

Is it your standard procedure to only upgrade ~1 time per year? It's pretty easy (in my experience managing my company's production environment as well as lower environments) to get into a cadence wherein you hit basically all of the quarterly upgrades - choosing a lower environment to upgrade very early, doing some QA/Regression testing in that environment for a week to a few weeks, then once you're satisfied, upgrading your remaining environments.

Keeping in-step with the appian dev pipeline in this manner takes a lot of the fear out of making a big jump, IMHO.

RE: Need feedback on 26.6 upgrade

Shubham Aware — Wed, 15 Jul 2026 06:21:18 GMT

Low risk. Appian Cloud upgrades are managed and backward-compatible, so 25.3 to 26.6 should not break records, process models, or connected systems.
Recompile/test custom plug-ins and read the removals sections of every release 25.4 to 26.6, then upgrade a lower environment
Run Health Check in your lower environments before and after the upgrade to catch plug-ins using deprecated/removed APIs and design or config risks.

RE: Need feedback on 26.6 upgrade

Stefan Helzle — Wed, 15 Jul 2026 06:19:28 GMT

In the last 16 years, Appian upgrades have been extremely stable. But you mention plugins. This is something you should check.

We upgrade our first environment tomorrow.