How to prevent concurrent flow run triggered by REST API - Asynchronous call?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2023 12:57 AM
Hello Dear Service Now experts,
Perhaps, someone could give a hint on how to overcome the following difficulty. I have a workflow that is triggered by REST API call. The purpose of a workflow is to create an incident record for AZURE Service Health alerts. The need is to have 1 record for a given Azure Tracking ID. The difficulty is that in case a Service Health alert is applicable to multiple subscriptions, it will call Service Now REST API for each impacted subscription simultaneously with the same Tracking ID. As a result there are flows running in parallel and these parallel flow instances create duplicate records. (Look up of a record with the correlation ID = Azure Tracking ID returns no records).
Is there a reliable way in Service Now flow to prevent such parallel runs?
There is a workaround to put random delay in the beginning of a flow but I was wondering if more elegant/reliable solution exists.