Flow-type Activity Sets missing (not even Pending) in HR Agent Workspace Playbook

vinayakbaba
Tera Contributor

Environment

  • ServiceNow HR Service Delivery — Lifecycle Events / HR Agent Workspace
  • Custom Lifecycle Event with 6 Activity Sets (stages). Two of the six stages contain Flow-type activities — the Activity Set item's fulfillment is a Flow Designer (sub)flow rather than an HR Task or HR Service.

Issue In the case's Playbook (HR Agent Workspace), only 4 of the 6 stages appear at all. The two stages built on Flow-type activities don't render — and unlike the other not-yet-reached stages, which correctly show as "(Pending)" placeholders, these two don't show up even as Pending. They're just missing from the list entirely.

What we've tried

  • Confirmed this matches KB1117067 ("HR Agent Workspace playbook doesn't show Flow Activity Types") — isolated to Agent Workspace; the native UI and Employee Service Center portal render the same activities fine.
  • sn_hr_le.exclude_activity_types already existed; edited it to remove "flow" from the CSV value.
  • sn_hr_ws.exclude_activity_types didn't exist at all, so created it: Global scope, Type = string, Value = content,activity_container (default list minus "flow"), Ignore cache = true, Private = false.
  • Flushed cache (cache.do) and fully closed/reopened the workspace tab rather than just refreshing.
  • Retested on a freshly created case. No change — the two Flow-based stages still don't appear.

Questions

  1. Is sn_hr_ws.exclude_activity_types actually what governs the Playbook's "upcoming stages" preview, or does that preview run on separate logic not controlled by this property — i.e., does the fix only apply once a stage is actually launched, not before?
  2. Has anyone gotten a Flow-type activity to render correctly in the Workspace Playbook through this property alone? Or did you end up routing it through an HR Task/HR Service instead, with the flow triggered off that record rather than being the Activity Set's fulfillment type directly?
  3. Any other property, cache layer, or Activity Definition setting we might be missing?
0 REPLIES 0