The user is currently getting this error when they try to use one of the dropdown fields on one of our environments, and the logs show this:
ERROR com.appiancorp.core.expr.SaveEncryption - Received a save which does not start with the expected save encryption salt.Any ideas what could be causing this sort of error?
Discussion posts and replies are publicly visible
Have you opened a support case for this issue? I would recommend doing that for this problem.
Thanks Alex, if the issue persists we'll do that.
Did you get to the bottom of this as we've recently started seeing the same message being highlighted in the Health Check reports (although no users have reported any issues)?
Hey Gavin, we didn't look into it any further I'm afraid, the issue occurred on our SIT environment so it hasn't caused any major issues and I haven't looked at it since. Sorry I can't be of more help.
We'd gotten a few scattered reports of this recently, so we looked into it further. We discovered that this is happening in a few edge cases where an interface would normally be refreshed, but didn't get the chance to fully refresh.
For example, someone enters an invalid input into an integer field with a default or placeholder value. They then immediately click submit, and then click submit again before the field has a chance to reset to the default value (which it would do when provided an invalid input). We are working on a fix for the issue, but I don't have a timeline that I can share at this point. However, I can say that the error, while confusing, is also entirely benign. A user can simply click "ok" if they see the error and continue with their work. We certainly do apologize for the inconvenience. Please let us know if you have any other questions or concerns.
Hello Eliot Gerson, we have started getting this error in our SIT env, though it has occurred only couple of times. Is there any update on this.
Has there been an update on this case? A few of our users have reported this error recently.
We are on 20.1 - has a fix been implemented on newer versions?
Eliot Gerson What's the latest updated and timeline for solving this bug? Is it solved in lasted production 21.2 version?
We are encountering same issue randomly on our record view with filter. Record view does not allow any refresh variable so it is quite weird error for us. We are using Appian version 20.1
"Expression evaluation error [evaluation ID = W0063286]: An error occurred while executing a save: Could not decrypt item of type SAVE_VALUE "
Yes, this issue should be resolved in the latest version of Appian.
© 2022 Appian. All rights reserved.