What should I do with the records in the Critical Updates[sn_critical_update]TBL?

bonsai
Mega Sage

‎06-18-2025 01:20 AM

When I upgraded, the subflow "Critical Update Instruction Flow" remained in a waiting state.

After investigating the cause, I found that it seems to be related to the Critical Updates[sn_critical_update] record and the Flow Data[sys_flow_data] record.

I thought that if I processed the Critical Updates[sn_critical_update] record, the Flow Data[sys_flow_data] record would be completed, but what should I do?

0 Helpfuls
  • 269 Views
1 REPLY 1

Community Alums
Not applicable

‎06-19-2025 10:46 PM

Hi @bonsai ,

  1. Go to All > System Policy > Critical Updates (sn_critical_update table).

  2. Find the update linked to your stuck subflow (check the name/description).

  3. If it’s stuck in "Not Started" or "In Progress":

    • Open the record and click "Mark Complete" (if available).

    • Alternatively, manually set the State field to Complete.

Option 2: Force-Close the Flow

If the update is already complete but the flow is still stuck:

  1. Navigate to System Definition > Flow Data (sys_flow_data table).

  2. Search for the flow’s record (filter by name or parent_sys_id of your subflow).

  3. Open the record and:

    • Set State to complete.

    • Set Execution Status to finished.

Option 3: Restart the Flow Engine (Nuclear Option)

If multiple flows are stuck:

  1. Go to System Diagnostics > Background Jobs.

  2. Restart the Flow Engine job (or flow_runner worker).

Preventing Future Issues

  • Check logs: Look for errors in System Logs > All (filter by source=flow).

  • Test in pre-prod: Always test critical updates in non-production first.

0 Helpfuls