Kick off external workflow that isn't child workflow

Community Support
1

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?

2

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.

3

Thanks for that, continuing execution was one of my concerns. Perhaps that’s the better way to do it.

4

Hi @tihomir, I have a similar issue. At first, I thought to create child workflows. However I would need to be to able to trigger 10k child workflows, and there is a limitation of 1k child workflow per parent workflow. What alternative do I have? I dont want to create 10 child workflows that have another 1k child workflows. Thanks for your help