I’d like to prevent duplicates based on a key when launching a child workflow. So if there has been a successful run I’d just like to skip starting it. I’m wondering if this is the right way to go:
I believe Cadence Java client had a bug that caused the parent to fail without hitting the catch block that surrounds the child invocation. Is it what happens to your workflow?
I’ve checked and it works fine in Temporal Java SDK. The following code snippet returns “Already running” if child with this ID already was executed: