Pipeline does not resume after implementing the DevOps change requestDescriptionFor DevOps change requests outside the 'DevOps Simplified' and 'DevOps' change models, the orchestration tool pipeline is expected to resume after the change request is either rejected, canceled, or implemented. Sometimes, however, the pipeline remains in a waiting state and times out. This can happen if DevOps change request approval flow is executed before the step execution is associated with the change request. DevOps offers the following out-of-the-box (OOTB) change request approval flows: DevOps Change Request Manual Approval FlowDevOps Change Request Advanced Automation Approval FlowDevOps Change Request Minimal Automation Approval Flow Steps to Reproduce Install DevOps Change Velocity. For more information, see Install DevOps Change Velocity.Create and configure an orchestration tool in ServiceNow DevOps Change Velocity. For more information, see Integrating DevOps Change Velocity with third party tools.Set up a pipeline with change acceleration, and track it in ServiceNow DevOps Change Velocity.Run the pipeline in the orchestration tool. It stops at the change acceleration step, and a change request is created in ServiceNow.Implement the change request. Expectation: The pipeline should resume in the orchestration tool. Actual: The pipeline keeps waiting. If a step execution is linked to the change request, it remains in a "Pending Decision" state.WorkaroundThe workaround is to include a brief delay using the "wait for duration" action before the step execution lookup step in the DevOps change request approval flow.Related Problem: PRB1948342