This article outlines the process to reset the Analytics Engines in self-managed installations of Appian.
NOTE: These steps should only be performed when advised to do so by Appian Technical Support. They should only be performed on the process analytics engine. These steps are not supported on any other engine.
Note: For the most up-to-date steps, always refer to the official Appian documentation. The steps below are provided as a reference for common deployment types.
Resetting the analytics engines on AoK requires a number of extra steps.
kubectl -n <namespace> scale statefulset appian-webapp --replicas=0
kubectl -n <namespace> exec -i --tty appian-service-manager-<engine>-0 -- ./serviceManagerScriptWrapper.sh services/bin/checkpoint.sh -s execution,process-design -w
kubectl -n <namespace> scale statefulset appian-service-manager-execution<XX> --replicas=0
kubectl -n <namespace> scale statefulset appian-service-manager-analytics<XX> --replicas=1
kubectl -n <namespace> scale statefulset appian-service-manager-process-design --replicas=0
kubectl -n <namespace> exec -i --tty appian-service-manager-analytics<XX>-0 -- ./serviceManagerScriptWrapper.sh services/bin/stop.sh -s analytics<XX>
kubectl -n <namespace> exec -i --tty appian-service-manager-analytics<XX>-0 -- ./serviceManagerScriptWrapper.sh services/bin/resetAnalytics.sh -s analytics<XX>
<APPIAN_HOME>/tomcat/apache-tomcat/bin/stop-appserver.sh
<APPIAN_HOME>/services/bin/stop.sh -p <SM_PASSWORD> -s analytics,execution,process-design
<APPIAN_HOME>/services/bin/resetAnalytics.sh -p <SM_PASSWORD> -s analytics<XX>
<APPIAN_HOME>/services/bin/start.sh -s analytics,execution,process-design
<APPIAN_HOME>/tomcat/apache-tomcat/bin/start-appserver.sh
This article applies to all versions of self-managed installations of Appian.
Last Reviewed: April 2026