- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2022 03:12 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2022 10:30 AM
Hi Smriti,
Flow Designer PM here...Flow Designer requires at least 1 Action or Subflow to 'activate' a flow.
However, there are two exceptions: you can build a logic-only flow if the logic includes either 'Call a workflow' or 'Dynamic flow'.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2022 03:45 AM
Also I have created an update set in global scope itself to capture this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2022 03:51 AM
Hi,
Did you try to create fresh flow and check if this issue comes for the new flow as well?
Did you try to clear instance cache using cache.do and then logout and login again?
Regards
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2022 03:57 AM
Yes I created a new one and it came there as well.
I think having 1 action step is necessary
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2022 03:58 AM
as per screenshot there is already 1 action which is IF
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2022 04:38 AM
That ideally comes under flow logic correct.
I just added send notification after waiting and the option to make it active is available now.