Azure DevOps — Skipped Pipeline Steps in Azure Interpreted as Failures in DevOps Change Velocity

[amarnath5001]

Dear Community,

We're working on a DevOps Change Velocity integration with Azure DevOps and have run into two related issues. I've done initial research and confirmed findings with our KB articles, but I'm looking for anyone who has dealt with a similar setup and found a ServiceNow-side solution.

Environment: ServiceNow Zurich, Azure DevOps (Cloud), DevOps Change Velocity

Issue 1 — Skipped Steps Registering as Failures

Our client's Azure pipeline has conditional steps that get skipped based on conditions defined in Azure. When these steps are skipped, ServiceNow DevOps Change Velocity receives them as "Failed" task executions. There doesn't appear to be any OOB status mapping to handle "Skipped" — ServiceNow only recognizes Successful, In-Progress, and Failed.

This causes the pipeline execution to show a red/failed state in ServiceNow even though the pipeline completed successfully on the Azure side.

Issue 2 — Piecemeal Pipeline Stops After First Stage

The client's pipeline is not a continuous flow. It consists of approximately 11 stages where each stage completes and then a script triggers the next stage. In ServiceNow, the pipeline stops progressing after the first stage. We believe this is a direct result of Issue 1 — the failed (actually skipped) steps in the first stage prevent ServiceNow from recognizing the stage as successful, which blocks downstream stages from being processed.

This is consistent with what KB1588561 describes: a DevOps pipeline is treated as a single entity, and any downstream issues in a stage (like incomplete or failed steps) can block the entire pipeline from progressing.

What We've Explored So Far:

Reviewed KB1588561 (incomplete step data blocking pipeline progression) — confirms the root cause chain
Reviewed KB2246217 (change stuck in progress due to waiting stages) — the "Get and Update Change" custom task approach is noted but doesn't solve the skipped-step classification
Reviewed KB2523967 (ACL-related pipeline failures) — ruled out as unrelated to our scenario
Confirmed there is no OOB property or configuration to remap "Skipped" to "Successful" in task execution status
Modifying the Azure pipeline (e.g., adding steps to normalize skipped results to Succeeded) is not an option for this client as they are unable to make changes to their existing Azure pipeline structure.

Option 2 - What we tried - Customize the inbound event processing to reclassify skipped steps as successful. This has been tried and is failing post configurations in Tool Capability mappings. 

What I'm Looking For:

*Has anyone dealt with a similar scenario and found a solution on the ServiceNow side? Specifically:

*Has anyone customized the orchestration inbound event processing subflow to reclassify skipped steps as successful?
*Is there a way to configure the pipeline step mapping in ServiceNow to ignore or exclude specific conditional steps?
*Has anyone successfully modeled a piecemeal/chained pipeline (where scripts trigger subsequent stages) in DevOps Change Velocity?
*Are there any DevOps properties or configurations I might be missing that could handle this?
*Any experience, workarounds, or pointers would be greatly appreciated. Happy to share more details about the pipeline structure if needed.

Thanks in advance.