Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

what are the Limitation on number of child workflow can be created via CreateSubOrchestrationInstance in Durable Task Framework? #1042

Open
kikeshar opened this issue Feb 12, 2024 · 0 comments

Comments

@kikeshar
Copy link

In My use case if I have to create large number of child workflow (~50k) for given workflow. From the wiki https://github.com/Azure/durabletask/wiki/Feature---Sub-orchestrations-(aka-nested-orchestrations) does not mention any limitation on number of child workflow. But I suspect there has to be some limit with respect to memory /CPU uses because all child workflow shares same context. Is there any guidance on max supported child workflow using DTF?

Also wondering if there are any demarcation on using separate workflow vs creating sub orchestration.

P.S - I understands these are more of queries than issues. If there is any other forum where I can get these queries answered. Please do mention it.
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant