Parm1 not fetching for SLA flow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2025 08:47 PM
Hi Gurus,
We've a strange situation here where our instance is domain separated and we're trying to use an OOB SLA notification flow, but it's not working. Please see below for full details:
Our Domain Hierarchy is as follows
Global | ||
TOP | ||
Enterprise Domain | ||
Shared Services | Dedicated A | Dedicated B |
We've a customer under Dedicated A domain for whom we've configured OOB Case, Incident, and Change Management. All our internal users(Assignment Groups and support agent users ) sit in Shared Services Domain. we've given shared services contains dedicated A, so they'll be able to create and access cases under dedicated A domain.
When a case is raised, case SLA notification is running in the Dedicated A domain. Once SLA is breached, it isn't able to fetch parm1 from Assigned to Field.
Kindly request someone to help in this regard.
Thanks in Advance

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2025 09:45 PM
Is the user in the assigned to in a different domain?
OOB the flow will run in the same domain as the task_sla. And task_sla inherits the domain of it's task record. Therefore, if the Case is in the 'Dedicated A' domain, the flow will only be able to access data that domain has rights to.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2025 08:58 PM
can we make the task_sla run in the shared domain where all users are available?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2025 04:03 AM
Not easily.
However you can create a flow action within your flow to run a subflow in another domain. The flow action would use a script to call ScriptableFlowRunner which has a 'inDomain' function