We have a dev and test env in our organisation. I have a workflow in dev env which is change the status reason according to custom type field.
Ex-if type is of risk then in status reason is set to risk. Below is image of workflow.
After importing this workflow in test env when I tried to activate it was showing this error.
[View:/cfs-file/__key/communityserver-discussions-components-files/761/log.txt]
I had this same problem, I followed the steps guided by @Vipin Jaiswal for the advanced location, then I just activated the workflow and it worked normally.
When we import a solution with a workflow that already exists, the original process is deactivated and replaced with the process included in the solution.
Due to some unidentified problem, it caused a conflict in the records during the deactivation of the original process, but when using advanced search the system located the substitute record (latest version) and allowed me to activate it normally.
Just check if you have multiple version of same workflow instance got created in the system
Use advanced find to find the workflow.
Refer this blog (which is for Business Rule) but was facing same problem
https://vjcity.blogspot.com/2019/05/deactivated-business-rule-running-in-ms.html
it seems like the status reason you used in workflow is invalid. I would go to status reason in your entity and check if the value on each label matches between dev and prod (Click Edit on the label and value will be right under label), if not, you need to export and import the field so that they matches.
Share
Report
All responses (
Answers (
95
