Guest Dave Stewart Posted October 3, 2018 Share Posted October 3, 2018 Hi I've recently rebuilt our New starter proc ess, creating a new capture and BPM. The Original BPM, which I've renamed to "avdc-starter-process-OLD", is no longer used by the Service however the attached error started to be thrown today. Wasn't the case before today despite our having the new process in place for weeks now. Link to comment Share on other sites More sharing options...
Victor Posted October 3, 2018 Share Posted October 3, 2018 @Dave Stewart : The reason why the error occurs is that when the request was raised on 11/09 it used the "avdc-starter-process" process which seems to no longer exists (as you said, you have renamed it) or is currently not active. The error occurred today because the process on this request was progressed and part of the progress was to "read" the "old" process which no longer exists. The error should not occur on requests raised after you rebuilt the starter process. Do you currently have an "avdc-starter-process" and an "avdc-starter-process-OLD" process? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now