Duplicate step execution record created for same task execution while using ServiceNow DevOps Change Automation custom action for Github.DescriptionCustomer has followed the below documentation and implemented ServiceNow DevOps Change Automation custom action and GitHub Environments for ServiceNow DevOps Change https://docs.servicenow.com/bundle/rome-devops/page/product/enterprise-dev-ops/reference/servicenow-devops-change-automation-for-github-actions.html#d3395e495 When we make any changes in the DevOps environment and deploy the changes to ServiceNow through pipeline, we could see duplicate pipeline executions. Duplicate step executions record created for same task execution while using ServiceNow DevOps Change Automation custom action for GitHub. Ideal behavior: It should update the existing step execution record and should not create another one.CauseThe pipeline execution has created 2 callback records, each associated with a different aspect of the pipeline execution. One callback record pertains to the environment, while the other is related to a custom change action.This conflicting setup have led to the creation of two step executions for the same task execution, causing the duplicate executions.ResolutionThe presence of a secret in the environment was causing the conflict.To address this, we recommend removing it from the environment and rerunning the pipeline.