Workflow getting initiated twice!

sharmavikrant
Kilo Expert

We have different workflow associated with our Change requests and each workflow has a different set of group approvals arranged in serial order. However, there is a strange activity which is taking place, If the change is in the first stage of approval and if someone updates the Change and approvals remains as it is. The change request repeats the same approvals that are associated with the first set of group approvals. However if the approvals reach the second stage of approval, the change request behaves normally . I have tried to investigate this and only been able to get to a conclusion that the workflow is initiated again, and no OOB business script is taking part in inserting the approval again.

 

Has anyone seen this behavior before? Or there is any OOB script that i should be aware of?

1 ACCEPTED SOLUTION

I don't think that is possible .. if the tables are mentioned , it will not get copied for everything .. are you sure that the workflows for requests were copied from clone and not newly created when something was updated on the request? check the created dates for the workflow instances and cross check those with the parent instance from which you are cloning ...


View solution in original post

10 REPLIES 10

akhil19
Kilo Expert

Hi,



Did you check if there any other workflow versions getting attached to the Change request once the Change is updated.



Thanks


Akhilesh


Michael Fry1
Kilo Patron

If you open a Change, and then look at your workflow, I'd start my investigation on that workflow activity. Maybe something isn't quite setup correctly there?


andrew_venables
ServiceNow Employee
ServiceNow Employee

What's the condition for the Workflow starting?


sharmavikrant
Kilo Expert

Thanks Guys for your responses. I believe there was a system issue. For some reason the workflow associated to the changes didn't get transfered to the test environment after the clone. And it was a clone from the Prod, it created a bit of a panic. I am not sure if this behavior is usual as the workflows associated   with the requested items didn't have any effect. Thanks for the help anyways.



But will sure look for any suggestion from anyone.