Flow Designer service catalog very slow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2021 12:25 PM
I have moved 3 of my workflows into Flow Designer. One of them is lengthy and complicated and two of them are smaller, ie depending on a certain request type I create catalog task or some I automate using a Powershell script. The larger one has multiple REST calls etc.
On submission all the flows take a long time to submit the catalog item and the larger one takes extremely long. I tried moving it to its own scope (that raises its own set of challenges with notification etc and access to certain global tables), but that didnt help.
Since ServiceNow is pushing everyone to FD, why would there be performance issues like this and any ideas as to what can be done?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-09-2021 02:56 AM
How complicated was your flow?
I dont know how to make the flow smaller than 50 steps.
I'm curious just so that I can provide more information to ServiceNow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-09-2021 04:15 AM
Hi,
I'm talking about flow process performance, not submitting the Catalog Item.
Currently we have approximately 20 ITSM flows and about 30 steps in each. Previously we also had much more steps, but we managed to optimized with Subflows and flow Actions.
In our case RITM task creation or Approval record take approximately 7 - 10 seconds. Not too much but this causes inconvenience in work because we have to reload form waiting for records creation during QA testing. Workflow creates the same records without any delay. For end user it's not critical and we can affords such performance.
Please keep me posted if Support suggest another solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2021 05:05 AM
We experience the same inconvenience as your QA team in our daily work. I think this is unavoidable, because the whole Flow Engine was built upon the concept of being async, using events. The only "solution" we found for this is to set up ATF tests for our most important flows/catalog items and let ATF do the QA testing instead of us.