New Capability: Non-Employee Risk Management - In-flight workflow session continuity

Announcements Product News
, , ,
1

:speech_balloon: Aha! Ideas Portal

This new capability is brought to you by Aha! Idea :aha: NE-I-167 — Workflow changes lead to request termination which addresses workflow configuration changes canceling in-flight sessions.

:sparkles: Description

For Non-Employee Risk Management workflows, administrators can update workflow configuration while people are already moving through a workflow—those in-flight sessions are no longer ended solely because the workflow definition changed.

:red_exclamation_mark: Problem

Until now, when you change a Non-Employee Risk Management workflow configuration, active workflow sessions are often canceled. Teams wait for work to finish before making improvements, or they accept disruption and rework. That slows iteration and creates friction for admins and participants.

:light_bulb: Solution

How it worked before

  • Saving changes to a Non-Employee Risk Management workflow typically stopped or invalidated active sessions tied to that workflow, so people could not continue the same run, even with the initial configuration.
  • Admins often had to time configuration changes around open work or accept that in-flight work would be interrupted.

How it works now

Admins can iterate on workflow design without having to clear the queue of active work first—within normal product rules and guardrails.

  • When you save changes to a Non-Employee Risk Management workflow, sessions that already started keep running using the workflow definition that was in effect when each session started (steps, branches, and behavior as defined at that time).
  • New sessions started after your change use the updated workflow definition.
  • Workflow sessions will not be canceled because an admin published a configuration change; what requesters and approvers are able to perform in the session is consistent with the version of the workflow their session was bound to.
  • The workflow version in use for a session is recorded and visible in workflow execution logs, accessible from the Workflow Tracing UI, so admins and support can see which definition a run executed against when reviewing debug output.

:busts_in_silhouette: Who is affected?

  • Customers who use Non-Employee Risk Management workflows (administrators who configure workflows, and users managing/interacting with requests

:date: Important dates

Customer sandbox availability: June 2, 2026
Customer production rollout begins: June 8, 2026
Customer production rollout completes: June 19, 2026

:books: Resources

  • Documentation: [link to only become available when feature in Prod]
2 Likes
2

UPDATE 5/18: we are delaying the Sandbox and Production rollouts of this feature by one week, respectively. The new dates are

Sandbox: May 18, 2026
Production: June 1, 2026

We apologize for the inconvenience.

3

UPDATE 5/21

To ensure quality and stability of this feature, we are disabling this feature in Sandbox tenants in which it was previously enabled. The behavior of workflow updates has reverted to the previous behavior prior to this feature.

We will re-enable in Sandbox next week, and will keep you posted on the new Sandbox re-enablement date.

Production tenant enablement is now set to begin June 8, 2026

We apologize for the inconvenience.

2 Likes
4

@jeff_lakey , Do we know when this will be enabled back on sandbox?

5

Is this enabled in production?

6

UPDATE June 10

Hello everyone.
To ensure optimal performance and stability, we are taking a phased approach to enabling this feature across our production environments. We expect the rollout to be completed for all tenants by the end of next week: Friday, June 19

1 Like