I have encountered the following scenario which breaks the change process leaving it stuck in assess/auth:
Approval rule: one approver from each group or any reject - created by 'ask for approval' flow action
- lets say we have 2 group approvals pending
- user_1 from group_1 approves the change - all other group_1 users approvals are set to 'no longer required'
- user_1 changes their approval to 'not yet requested' - done accidentally and not noticed.
- user_2 from group_2 approves the change
- all groups have now provided an approval response - the flow processes this
- because one response is neither an approval or rejection ('not yet requested') the ask for approval result is set to 'cancelled'
- As there is nothing to handle this the flow ends but the change does not transition states forward or backwards
- The change is now stuck in assess/authorize with approvals and flow completed - there is no way to 'unstick' this change record.
I can add a check to all the assess/auth flows to see if the 'ask for approval' result is neither approve or reject and take some action at this point. However, it is a lot of work just to try to catch a very unlikely scenario so it doesn't feel like a great solution.
Considering this scenario - how should it be handled? What is the correct approach to ensure the change/flow cannot get into this state? Can you provide any other insight?
