You are currently reviewing an older revision of this page.
An interface loads in /design with the following error:
One or both of the following errors are also present 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
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)
The context size is too large, which is due to too much data being stored in load() variables in the interface. There is a 200MB limit to the uncompressed context a load() variable can hold for security purposes.
Make changes to the interface sail code, or to the expression rules it uses, to reduce the interface's context size. This requires reducing the amount of data 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