You are currently reviewing an older revision of this page.
An interface loads with the following error:
Switching to expression mode also shows this error in the application server log:
ERROR com.appiancorp.sail.BindingsEncryptionHelper - Caught context exception: java.io.IOException: Max decompression size reached!....ERROR com.appiancorp.rest.shared.AppianExceptionMapper - Internal Server Error on REST API invocation.com.appiancorp.exceptions.LocalizedAppianRuntimeException$LocalizedAppianException: Cannot interpret context for UI expression. Reason: Bindings
and / or
ERROR com.appiancorp.sail.BindingsEncryptionHelper - Caught context exception: java.io.IOException: Max decompression size reached!....ERROR com.appiancorp.sail.StatefulUiStateWithStatelessFailover - Unable to deserialize bindings using Stateful UI State...reverting to Statelesscom.appiancorp.suiteapi.common.exceptions.AppianException: Cannot interpret context for UI expression. Reason: Bindings (APNX-1-4215-002)
There is a 200MB limit to the uncompressed context that we put in to prevent a theoretical security vulnerability.
The size of the context is too large, too much is trying to be stored in load().
Reducing context size almost certainly means cutting back on what is stored in load() variables.
Optimize sail code to reduce the amount of information stored in load() variables
It may not be possible to edit the interface directly due to the error itself. If this is the case, follow one of the below workarounds to make changes to the interface.
Prevent expression rules that are returning a large number of data from evaluating.
If the interface exists in another environment not experiencing this issue, make changes to the interface in the working environment and import it.
This article applies to Appian 17.1 and later.
Last Reviewed: December 2018