Activity on child workflow is not retried when parent workflow abandoned the child

Hi Team,

I have a use-case of triggering a child workflow asynchronously from a parent workflow, and the parent workflow doesn’t wait for the child to complete. Now is the aysnc execution of the child workflow if any of the activity fails, it doesn’t retry though I have defined retry options for the activity. The same activity however when triggered from the parent workflow, retries as per the defined retry policy. Is any additional configuration required to enable retries of activities for abandoned child workflows ?


One observation that I have for the worker that is executing the child workflow is that, it doesn’t handle activities, but for the parent and other child workflows that completed synchronously, the activity handler for the worker had a check mark against it.

Found the issue. I didn’t add some of the activities in the childWorkflow worker, which caused it to behave differently.