We’re experiencing recurring high memory usage in our Appian Cloud DEV environment that is leading to emergency restarts. This typically occurs outside of normal development hours, when there is little to no active user activity.
As part of troubleshooting, we have:
Cleared all processes that had stopped due to exceptions
Removed older versions of process models and interfaces
Reviewed for obvious runaway process instances
Reviewed guidance in KB-2011
Despite this cleanup, the memory spikes continue.
Has anyone encountered similar behavior in a DEV environment with low user activity? If so:
Were scheduled processes, integrations, or unattended background jobs the root cause?
Are there specific logs or metrics in Appian Cloud that are most helpful for identifying memory drivers?
Does exporting and removing older, inactive applications from DEV meaningfully reduce memory consumption, or is memory primarily driven by actively executing objects?
Any guidance on deeper diagnostics or best practices for isolating memory usage in Appian Cloud would be greatly appreciated.
Discussion posts and replies are publicly visible
High memory spikes in Appian Cloud often stem from unarchived processes, excess object versions, and unattended scheduled jobs running outside dev hours.Check Health Check report and Monitor the Process Metrics to identify culprits.Export inactive apps to cut versions, archive old processes, review schedules, then contact Support for diagnostics.https://community.appian.com/support/w/kb/1574/kb-2011-how-to-address-high-memory-usage-in-appian-cloud-environmentshttps://docs.appian.com/suite/help/26.2/understanding-the-health-check-report.html