Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
+1
person also asked this
people also asked this
Replies
13 replies
Subscribers
6 subscribers
Views
5046 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Wrong Process Model version is picking up
Rama Thummala
Certified Lead Developer
over 7 years ago
Hi,
I have a process model with multiple versions. All the versions are published and in disabled mode except the latest version.During the run time expecting to pickup the latest version, but surprisingly old version is getting picked up.
I tried clean up the server and restarted,but facing the same issue.
Any suggestions?
Thanks
OriginalPostID-253933
Discussion posts and replies are publicly visible
0
Mike Schmitt
Certified Lead Developer
over 7 years ago
I have experienced the same issue lately - I've been working with Appian via a support case.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
reginaldm377
over 7 years ago
To be clear, you're only experiencing this with newly created process instances correct?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Venu
over 7 years ago
@Rama
i think you might have saved as 'save new version' from process instance editing mode, So it creates new version of your process model say 1.1 if your published version is 1.0. Give a try by publishing process model again, hope it will helps.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Rama Thummala
Certified Lead Developer
over 7 years ago
@reginaldm377
Yes, it is with newly created process instances.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Rama Thummala
Certified Lead Developer
over 7 years ago
@venu
I have verified the versions(all are in disabled mode) and published multiple times, but facing same issue.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Rama Thummala
Certified Lead Developer
over 7 years ago
@mschmitt
Please let me know once the issue got resolved.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Mike Schmitt
Certified Lead Developer
over 7 years ago
@Ramanjaneyulut: out of curiosity, when the wrong version of the subprocess is being picked up, was the parent process instance already running at the time the new subprocess version was published, or is it also happening for new instances of the parent process (i.e. launched after the newer subprocess version was saved)?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
reginaldm377
over 7 years ago
Run through your knowledge center and double check for any duplicates of the process model exist
Also, idk if the process model in question is standalone or a subprocess of another, but maybe try doing a recall of the process model everywhere you can think of (if it's an action, then reset the call in your application package, in the process models you're calling this sub-process, etc.)
I'll try to think of other solutions if none of that works.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Mike Schmitt
Certified Lead Developer
over 7 years ago
Hey Reggie -
Just FYI, in my case I have a simple parent process model that loops over a particular subprocess, and as long as the parent process is running the same instance, it will continue to launch the version of the subprocess that existed when the parent was launched. If a new instance of the parent is launched, then the subprocess version launched will change to the existing one at the time of the new parent being launched. As far as I can tell this isn't an issue of duplicate process models / subprocess node setup issues / etc; it appears to be an appian engine issue, and I think engineering is now looking into it. -Mike
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
reginaldm377
over 7 years ago
You're experiencing this on which version Mike? Also, thank you for the info! I'll have to keep this in mind with the environments I'm working in the case I run into the same issue (assuming the issue is appian version based). Hope you're doing well!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
>