Flows stuck during upgrade

bonsai
Mega Sage

‎05-27-2025 07:23 PM

During the upgrade, the following flows were pending and did not complete.

Does this occur every time I upgrade?

Also, is it okay to cancel these flows?

・Critical Update Instruction Flow
・SC Best Practice Flow

・critical_update_end_of_support_glideencrypter_api

 

 

The following flows do not appear to exist, but context records have been created.

"critical_update_end_of_support_glideencrypter_api"
"task_steps＿1～27" *There are 27 records with numbers 1～27 assigned
"steps"
"steps_2"

0 Helpfuls
  • 288 Views
1 REPLY 1

Omender Singh
Tera Guru

‎05-27-2025 09:39 PM

Hi @bonsai , 

 

Please have a look to my response below:- 

1. Do These Flows Always Remain Pending During Upgrades?

It's not uncommon for certain flows to remain pending during upgrades. This can occur due to various reasons, such as:

  • System Resource Constraints: During an upgrade, system resources are heavily utilized, which might delay the execution of some flows.

  • Flow Dependencies: Some flows might be waiting for specific conditions or dependencies to be met, which could be affected during the upgrade process.

  • Upgrade Sequencing: The order in which components are upgraded can impact the initiation or completion of certain flows.

Therefore, while it's not guaranteed that these specific flows will always remain pending during every upgrade, it's a possibility that can occur under certain circumstances.

2. Is It Safe to Cancel These Flows?

Cancelling flows should be approached with caution. Here's a breakdown:

  • Critical Update Instruction Flow: This flow is essential for applying critical updates. Cancelling it might prevent necessary updates from being applied, potentially leaving the system vulnerable or unstable.

  • SC Best Practice Flow: This flow ensures that best practices are enforced within the Service Catalog. Cancelling it might lead to inconsistencies or deviations from established standards.

  • critical_update_end_of_support_glideencrypter_api: This flow likely pertains to the deprecation or end-of-support for the GlideEncrypter API. Cancelling it might result in deprecated APIs remaining active, which could pose security or functionality risks.

Before deciding to cancel any of these flows, it's recommended to:

  • Review Flow Contexts: Examine the flow contexts to understand their current state and any dependencies.

  • Consult Documentation: Refer to official ServiceNow documentation or support resources for guidance on handling these specific flows.

  • Test in a Development Environment: If possible, replicate the scenario in a development or test environment to observe the impact of cancelling these flows.

3. Understanding the Context Records:

The context records you've mentioned, such as:

  • "critical_update_end_of_support_glideencrypter_api"

  • "task_steps_1" through "task_steps_27"

  • "steps"

  • "steps_2"

These records are likely remnants or artifacts from previous flow executions or system processes. They might not correspond to active or existing flows but could still reside in the system due to incomplete executions or errors during the upgrade.

It's advisable to:

  • Investigate Each Record: Determine the origin and purpose of each context record.

  • Assess Dependencies: Ensure that no active processes or records depend on these context records.

  • Clean Up if Necessary: If confirmed to be obsolete and without dependencies, consider cleaning up these records to maintain system hygiene.

4. Recommended Actions:

  • Monitor Flow Executions: Regularly check the status of flows during and after upgrades to identify any that remain pending.

  • Implement Error Handling: Ensure that flows have appropriate error handling and timeout mechanisms to prevent indefinite pending states.

  • Engage with ServiceNow Support: If uncertain about the implications of cancelling specific flows or handling context records, consult with ServiceNow support for expert guidance.

By taking these steps, you can ensure that your ServiceNow environment remains stable and that any issues arising from pending flows during upgrades are effectively managed.

0 Helpfuls