I'm encountering a scenario where a race condition is occurring.
To elaborate, there's API1 responsible for creating a record in the database, while API2 updates the same data in the database. Both calls are received almost simultaneously, failing to record because sometimes it updates the data while the record is being inserted/processed.
This is a typical issue in operating systems and programming. While it can be addressed through programming and some adjustments, I'm curious if Workato offers any out-of-the-box solutions similar to wait-notify.
Best regards, Thanks in Advance.
Solved! Go to Solution.
I don't know if there are any out of the box solutions for this, but in my opinion this can be solved with the right recipe design.
Ideally both APIs would trigger the same Workato recipe, and you could sequence the API calls within the recipe.
If you're unable to change the way Workato is triggered here are a couple of options, including a way to route both calls into a single recipe.
All recipes above would be async function recipes.
Thanks for the insight. Sure programmatically this is achievable; however, this is a fundamental programming and there should be a standard solution for that. While I worked on other iPaaS TIBCO, Mule for example a standard solution was given "wait-notify" or "crtical-activity-lock" mechanism. Could you please advise how to reach out to workato engineering team to raise the concern.