Clarify API-only concurrency and per-member limits - #1646
robinjhuang wants to merge 2 commits into
Conversation
… behavior Rename the Comfy Cloud Parallel Execution section to Concurrency Limits and state clearly that only API submissions run jobs in parallel: the UI runs one job per person, and Team/Enterprise plans give each workspace member their own concurrency. Mirror the same explanation under Pricing and subscription on the Comfy Cloud getting-started page, and update links to the renamed anchor. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MpPuwjxKzAXSqRQ7UdjEd9
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
🌐 i18n translation sync reminder@comfyui-wiki English documentation was updated in this PR. Please complete or schedule translation updates for the following files: Japanese (
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: 7 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 10 reviews per hour. 📝 WalkthroughWalkthroughThe documentation renames the concurrency section, clarifies UI and API execution limits, documents per-member plan limits, and updates API-key links. ChangesCloud concurrency documentation
Merge Risk: ⚪ Minimal · up to This documentation-only change clarifies concurrency behavior and updates API-key links without identified production or user-impacting risk. 🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
Replace "your Comfy workspace" wording so API key creation points at the Developer Platform (platform.comfy.org) by name. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MpPuwjxKzAXSqRQ7UdjEd9
wei-hai
left a comment
There was a problem hiding this comment.
The API/UI clarification and updated links look good. One correctness issue needs fixing in both new per-member paragraphs before this is ready. Reviewed the latest diff and checked the concurrency admission behavior; no local test suite was run for this prose-only change.
| The Comfy Cloud UI does not support running more than one job per person. Workflows queued in the editor run one at a time, in order. Only API submissions run in parallel. See [pricing plans](https://www.comfy.org/cloud/pricing?utm_source=docs&utm_campaign=cloud-api) for subscription details. | ||
| </Info> | ||
|
|
||
| On Team and Enterprise plans, concurrency is per member: everyone in the workspace has their own concurrency limit, so one member's running jobs never block another's. |
There was a problem hiding this comment.
[P2] Keep the shared workspace cap in the concurrency explanation
Per-member limits are still subject to an aggregate workspace concurrency cap. Once other members fill that cap, another member's jobs queue even if that member has no running jobs, so "never block another's" promises isolation the product does not provide. Please describe the per-member limit as subject to the workspace's overall limit, and make the same correction in get_started/cloud.mdx.
Summary
Updated documentation to clarify that parallel job execution is an API-only feature and to explain per-member concurrency limits on Team and Enterprise plans.
Key Changes
Notable Details
https://claude.ai/code/session_01MpPuwjxKzAXSqRQ7UdjEd9