Pipeline Changes are closed but still showing Active = True

[SayanG838505890]

Hello Team, We have encountered some strange issue with the Pipeline Changes,
Some of the Pipeline changes that are closed but still showing Active = True. What will be the issue? Thanks in advance

[Samantha-JaS]

Hi,

Thanks for posting, I have added this response to your other thread on the same topic so you have it in both places.

This behaviour is usually not specific to Pipeline Changes, but relates to how the Active flag is managed when a record transitions to a closed state more broadly.

Active is not automatically derived from State

In ServiceNow, the Active field is typically set to false by platform logic for task-based records, or by a Business Rule or workflow when a record reaches a closed or cancelled state. If that logic does not execute for any reason, a record can remain Active = true even though it appears closed. These are two independent fields and do not always update together automatically.

Closure logic may be bypassed

Pipeline Changes are often updated or closed programmatically, for example via DevOps integrations or automation. If the normal closure logic does not run as part of that process, the Active flag may simply not be updated. This is one of the more common causes of the behaviour you are describing.

Customisations and integrations can interfere

Custom workflows, Business Rules, integrations, or updates arriving from external tools can all affect when or whether the Active flag is set correctly. If changes are being closed via an integration or background process rather than through the standard UI flow, it is worth checking whether the closure logic is being triggered consistently in those paths.

Custom state configuration

If a custom closed state is in use and it is not recognised by the platform's inactive state logic, records can remain Active even though they appear closed. This is worth confirming if your instance uses states beyond the out of box configuration.

Suggested next steps

• Verify whether the standard closure logic for Pipeline Changes is executing consistently across both manual and automated closure paths
• Check whether updates are arriving from integrations or background processes that may bypass standard Business Rule execution
• Review whether any custom states or overrides are in place that the platform may not be treating as inactive
• If the issue is widespread or persists after reviewing the above, ServiceNow Support will be able to review instance-specific configuration and logs that are not visible from here

---

Without visibility into your instance configuration, integrations, or any custom logic running on Pipeline Changes, it is not possible to point to a single root cause from here. The issue is usually related to closure logic not being triggered rather than the state value itself, but the specifics will depend on how your instance is configured.

Hope this helps point you in the right direction. If it does, please mark it as helpful or accept it as the answer on either thread as it helps others in the community find relevant answers more easily.