Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. 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.
I am trying to start the process model via the interface and was able to do it successfully, everything was working fine but right before the release, it has started showing an error when I click on the button to start that process model.
(Note that: no changes were made to the interface or process model after successfully running the tests and another important thing is no other smart service except a!startProcess is being used in the saveinto part of the button)
The following error is displayed in the designer mode after clicking on the button to start the process model
Interface Definition: Expression evaluation error: An error occurred while executing a smart service: Failed to start process. Process Model ID: 21506. This error will not be displayed to the user viewing this form. Click here to dismiss the error message and see the resulting interface.
Any help will be really appreciated,
Thanks
Discussion posts and replies are publicly visible
There are few thoughts that i can give you.1.- Save and publish your process model. (Deleting the latest version sometimes causes some weird behavior).
2.- Check your process model security.
3.- Verify your inputs on the process model.
rechecked everything, but the process model is not starting.now I have heard from my co workers that non of their processes are starting from interface via smart service
We had same problem. Couple of engines were down. We restarted server to make sure all engines are up and running. It resolved the problem.