For long running activities we can use heartbeats to notify whether the activity is running or dead.
We have a workflow that invokes multiple child workflow with some params based on grouping which the parent workflow generates. The child-workflows are long running workflows.
Is there a way to have similar heartbeats sent from child workflows, as these workflows are long running with timeout set as a few hours ? Or rather what is the way to notify the child workflow is running ?
We are using the go-client for implementing the workflows.
Long running activities heartbeat to ensure their timeout in case of a worker failure.
Workflow worker failure doesn’t lead to workflow failures. So heartbeating is not necessary.
Answered By – Maxim Fateev
Answer Checked By – Willingham (GoLangFix Volunteer)