Hello Celigo Community,
I am experiencing a race condition issue in my integration flows that involve Salesforce Account and Address records. When an Address record is saved, it simultaneously triggers an update on the associated Account record. Both real-time flows, for Account and Address records, execute an HTTP patch to update the same "Customer" record in Business Central. Due to the simultaneous execution of these two flows, I am encountering a race condition where one of the flows returns an error stating that the record has already been saved.
I have tried adjusting concurrency settings, but the issue persists. I would like to ask the community for any suggestions or best practices in handling such race conditions. Specifically, I am looking for a way to delay the trigger of the Account record when an Address record is saved, or any alternative approach that can help maintain data integrity while avoiding race conditions. I know this community has been asking for a delay function, but it's not yet available.
So, I am asking:
If you have encountered a similar issue or have any insights on resolving this problem, your input would be greatly appreciated. I am open to exploring different solutions to ensure the smooth functioning of our integration flows.
Thanks for your help!
Please sign in to leave a comment.