How to limit the concurrency of Flows triggered
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2023 10:23 PM
Hi All,
We have a requirement where when a csv file is attached to a change request, the system should process the file and insert few records into a table. This is done through Flow Designer and the trigger is on the attachment table.
Once the functionality is available to the end users, there are so many attachments will be attached to the different change requests.
Is there a way we can limit the concurrency on the flows gets triggered? for better system performance?
Regards,
Vasanth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2023 10:46 PM
Hi @Vasanth Pandia1 ,
Yes, it is possible to limit the concurrency on Flow Designer flows triggered by attachments to improve system performance in ServiceNow.
One approach is to use the "Concurrency Limiter" action in Flow Designer. This action allows you to limit the number of concurrent executions of a flow, so that only a certain number of executions can run at the same time. This can help to prevent overload on the system and improve performance.
To use the "Concurrency Limiter" action in your flow, follow these steps:
- Open your flow in Flow Designer.
- Locate the point in your flow where you want to limit the concurrency, for example after the trigger that fires when an attachment is added to a change request.
- Drag the "Concurrency Limiter" action onto your flow canvas and connect it to the previous action.
- Configure the "Concurrency Limiter" action with the maximum number of concurrent executions that you want to allow.
- Connect the "Concurrency Limiter" action to the next action in your flow.
- Save and activate your flow.
When your flow is triggered by an attachment, the "Concurrency Limiter" action will limit the number of concurrent executions of the flow based on the configuration you set. This can help to prevent performance issues caused by too many flows running at the same time.
Note that you may need to adjust the maximum number of concurrent executions based on your system's capacity and the resources required by your flow.
Regards,
Teja
If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2024 08:07 AM
Hi Teja,
I have the same question as Vasanth but I also do not see a "Concurrency Limiter" action. Is this tied to a specific plugin or is it a custom action? Any elaboration would be appreciated.
Thanks,
Riley
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2025 06:30 AM
Hi @Teja11 ,
I don't see any "Concurrent Limiter" action. Did you create this as a custom action? Can you please explain how you set that up?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2023 06:18 PM
Hi Teja,
Many thanks for your reply. I don't see any OOB action "Concurrency Limiter" within the now platform. you meant to create a custom action?
Regards,
Vasanth