Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Hi everyone,
The matter is that a process model that was working fine, suddenly shows the notification "process model is not valid" when open the process model, but it doesn't show more info about it. I'm pretty sure about it happened because we have modified some rules and interfaces, but this is a large process.
So, is there any way to take a log of the validation process to get the bug?
Discussion posts and replies are publicly visible
1. You can check if there are any issues in the newly updated rules on which the PM is dependent. Sometimes the expression editor isn't able to catch the error. Better to test all the scenarios in the rule itself.
2. You may check the tomcat-stdOut logs to see if there is a more descriptive error message available in it.
In Designer, bring up a list of all of that process model's Dependents. Then, in order of Last Modified, go through any Expression Rules and Interfaces, and check for any items that were saved in an invalid state (like throwing an error by default or saved with a syntax error that immediately displays in the rule editor window). That's your most likely source, as far as I can tell.
Agree with Mike, I only see this error when an interface is throwing an error itself - start there.
Thank you, Mike! It was exactly what i did, and I find out that an expression rule was saved even when showing an error.
you can go to process model and try to save it. it will show you the error if there is any in the expressions or the interface.