Async Subflow Processing the same data

Unknown

Async Subflow Processing the same data

Unknown

I have an async subflow that processes a Documents ID and creates Case IDs. Once the Case ID is created as a part of the process, we set its state to Processed. For some reason when we are looping through this subflow, we are seeing an issue where multiple Case IDs are being created for the same Document ID. How is this possible?

A scheduled job for processing data from a database. This job would result in eliminating any duplicate data from a list by merging the duplicates. However, since yesterday, the job is not picking up the unprocessed data and not merging the duplicates.
[i]edited by maxwell3000 on 7/10/2020[/i]

Unknown

[color=rgb(29, 28, 29)][font=Slack-Lato, appleLogo, sans-serif]The problem with async can come when youre looping over async subflow and firing off a bunch of work, but youre also not marking or flagging that work as "picked up". Then if the job runs again, it has no way of knowing, so it will blindly repeat old work. Which is likely to be occurring given your use case. [/font][/color]
[color=rgb(29, 28, 29)][font=Slack-Lato, appleLogo, sans-serif]
[/font][/color]
[color=rgb(29, 28, 29)][font=Slack-Lato, appleLogo, sans-serif]To resolve, I would recommend setting some state as the first step inside the async subflow. Not having this as the first step risks that if an error occurs, then causing the state to not be set. If the status isnt set then the scheduled job will continue to pick up the same data and read it as if it hasnt been processed. [/font][/color]