Approval getting auto cancelled in workflow?

[suresh40]

Hi All,

My group approval cancelled automatically in workflow please help me on this .

 

[Ravi9]

when u hover on the cancelled context what do u see , can u share some screenshots ? 

[suresh40]

Hi Ravi,

Sure, i will share.

[Michael Heilman]

I had a similar thing happen and it turned out that my custom States, for a table that inherits from Task, were getting ignored.

I had six custom States configured in the dictionary entry of State for my custom table, with values of 1-6. There are over a 150 Choice values spread across a dozen or more tables, so this is a normal way of extending choices for a table that inherits from Task Here is what the values look like for just my custom table and for Task:

Label	Value	Table
Planned	1	Audit Item [u_audit_item]
In Progress	2	Audit Item [u_audit_item]
Fulfilled	3	Audit Item [u_audit_item]
Departmental Approval	4	Audit Item [u_audit_item]
Coordinator Approval	5	Audit Item [u_audit_item]
Ready for Auditors	6	Audit Item [u_audit_item]
Sent to Auditors	7	Audit Item [u_audit_item]
Accepted	8	Audit Item [u_audit_item]
Pending	-5	Task [task]
Open	1	Task [task]
Work in Progress	2	Task [task]
Closed Complete	3	Task [task]
Closed Incomplete	4	Task [task]
Closed Skipped	7	Task [task]

Right before we get to the first approval step, I set the State value to '4,' Departmental Approval, however the workflow engine was reading a '4' as Closed Incomplete and was canceling the approval and ending the workflow. We fixed this by changing the values of the custom States, so they could no longer be confused with the default Task states:

Planned	100	Audit Item [u_audit_item]
In Progress	200	Audit Item [u_audit_item]
Fulfilled	300	Audit Item [u_audit_item]
Departmental Approval	400	Audit Item [u_audit_item]
Coordinator Approval	500	Audit Item [u_audit_item]
Ready for Auditors	600	Audit Item [u_audit_item]
Sent to Auditors	700	Audit Item [u_audit_item]
Accepted	800	Audit Item [u_audit_item]

This strikes me as a bug, that when referencing the State Choices table, ServiceNow should only be looking at the Choices for the table in question. In any case, easy to avoid.