From my experience looping back will always reuse the existing record. A way I solved this was via script (if you would want to allow the users to go through multiple of iterations) or via create task activity. Something like this:
But it also depends on what you would like to do after the second created task.
I am basically trying to create an approval process using a task - I'm needing more than just an "Approved / Not Approved" response. I need numerous fields completed as part of the approval process before this change progresses which is why I dismissed the normal approval process for this one. I am creating a task containing various mandatory fields, along with an "approved / not approved" question, If it isn't approved, then it is sent back round for the change to be amended. It's very important that if it isn't approved, for the responses to be logged in the ticket, which it currently does, but we could really do with the closed "Not approved" task being left there as evidence of the change ticket's journey before being eventually approved.
