Hi Michael,

Apologies it might not have been clear.  This workflow is for the template proposal.

I've seen OOTB that if the approval was rejected it would just cancel the whole proposal, but our Change manager requires that it returns back to the 'New' state as most of the rejections will be due to things missing from the proposal i.e. the user needs to add more detail in a specific field, rather than purely rejecting that the proposal should not become a template.

I think I have found what is causing my issue.  We have a business rule on the 'Task' table which cancels workflow if it hits a certain state value of '4'.  For the std_change_proposal table this is the 'cancelled' state.  

In my workflow I was setting the approval to 'rejected' before the rollback.  It was meant to change it back to approval = 'requested' after the wait condition it was failing at.  I've just removed this approval = 'rejected' step and this seems to have fixed the issue.  It appear that some script was changing the state to '4' - cancelled when the approval = rejected (not found this script yet).

On rolling back approvals what is best practice.  Should you mark it rejected as I had and then change it back to 'requested' at the relevant point in the workflow?  If I just leave it as  approval = requested when a user rejects and it hits the rollback will I encounter any other issues?

Thanks

Sam

Thanks

Sam