Thanks for raising this in the Community.
Were you able to determine the root cause of this error? If yes, please share the solution here, it might just help others out.
If this is still an issue you can open a support ticket here https://support.landesk.com/CaseLogging.aspx
1 of 1 people found this helpful
I am still in contact with Support at the moment regarding this. They are taking a look at my database to help find the root cause in our Incident process.
For the Request process we were able to get around this error by adding a dummy action to the process then saving. This then allowed us to take a copy of the process without hitting the error above.