duplicate approval record generated when manage approval by flow with 'go back to' logicIssue More than 1 approval record is generated when processing approval by flow for a task.SymptomsThe flow uses 'goback to' logic to move to the first place when reject the approval request, reject in the task record and it would generate more than 1 approval request record. Typically, one record is in the 'Requested state, and the other is in the 'No Longer Required' state.ReleaseAll release.CauseLegacy approval engine is still working when the user wants to manage the approval process by a customized flow or workflow.ResolutionThe legacy approval engine should be off once the approval process is managed by a flow or workflow. Approval Engine can be found by: Navigator -> Approval Engine