Deployment package not reflecting the new code changes in an appian cluster environment

Kindly describe the process that you are following for deploying.

We will be able to help if you elaborate your issue.

We are having a 3 node cluster for an appian environment, we are noticing that when we deploy a complete application level package deployment the latest changes are not reflecting in the environment, very simple rules wherein a change in one dropdown value opens up another rule, even these changes are not getting reflected, this is happening after around 3 months of successful deployments & QA validation. It shows some older version rules on the environment, giving us some suspicions that somewhere its caching the previous versions of the codebase & its unable to clear it.

We were suggested to try the below to clear the app server cache but it didn't help

community.appian.com/.../kb-1232-how-to-clear-the-application-server-cache

Have anybody noticed this behavior ? I will be very surprised if am the only one seeing this issue.

We are having a 3 node cluster for an appian environment, we are noticing that when we deploy a complete application level package deployment the latest changes are not reflecting in the environment, very simple rules wherein a change in one dropdown value opens up another rule, even these changes are not getting reflected, this is happening after around 3 months of successful deployments & QA validation. It shows some older version rules on the environment, giving us some suspicions that somewhere its caching the previous versions of the codebase & its unable to clear it.

We were suggested to try the below to clear the app server cache but it didn't help

community.appian.com/.../kb-1232-how-to-clear-the-application-server-cache

Have anybody noticed this behavior ? I will be very surprised if am the only one seeing this issue.

We are working with Appian support on this "454260 - Old code base showing after package deployment" but if someone has any clues it will greatly help.

Just to help others, we were informed by apian support to use the "force" option using a property file to import the package as a workaround but the investigation led no where.

I would although will not buy this theory but right now we don't have a choice, if anyone have seen this behavior, please do report on the forum.

Thank you