I’m currently starting workflow B from workflow A. Workflow B is not a child workflow. I’m doing so by injecting a temporal client into a “StartFlowB” activity and executing the flow via the injected client. Is this the recommended way to accomplish this or is there a better way?
Hi @Eric_Swann, yes you can use client in your activities, but not sure why you could not invoke B as a child workflow? If you want B to be able to continue execution after it’s parent A completes you can invoke B async with
ChildWorkflowOptions.ParentClosePolicy set to
ABANDON, see this post for description on how to do that with Go SDK.
Thanks for that, continuing execution was one of my concerns. Perhaps that’s the better way to do it.