Governance & Limits

Cloud Cooking gives you control over how source files enter the cook pipeline, and how many cook jobs a single creator can have running at once. This page aims to cover the available moderation for Cloud Cooking jobs, how to enable and use the CC Moderation Queue, and what Concurrency Limits are for.

The Cloud Cooking governance and limits page, allowing for content moderation and concurrency toggling.

Moderation models

Cloud Cooking supports two models for how a mod creator's source files enter the cook pipeline:

• No Moderation: Creators can submit source files for any platform, files are queued for Cloud Cooking without requiring admin/moderator approval first.
• Moderation queue: Submitted source files are held for admin/moderator approval before being queued for Cloud Cooking. This gives the team a review step ahead of the cook process, in addition to the standard moderation workflows applied to the resulting platform file.

Enabling and using the Moderation Queue

1. Once Cloud Cooking is enabled for your game, navigate to your Game Admin page > Cloud Cooking > Governance and Limits.
2. Enable the "Enable moderation queue" toggle and save.

Once the Cloud Cooking Moderation Queue is turned on, submitted source files wait for a moderator or admin to approve the user generated content before they are queued for cooking.

1. Navigate to your Game Admin page > Moderation > Cloud Cooking > Pending Approval.
2. As a moderator or admin, review the queued source files and approve the ones you want to proceed to Cloud Cooking.

Approved files are queued for Cloud Cooking as normal. Rejected files are not cooked, and creators can resubmit an updated source file for review.

Concurrency Limits

Concurrency Limits control how many cook jobs a single creator can have pending or running at the same time for the game. This prevents one mod creator from consuming a disproportionate share of the game's Cloud Cooking capacity.

This Concurrency Limit is set by the game studio and once configured, it's applied automatically for Cloud Cooking jobs.

The Cloud Cooking Settings Object exposes the configured limit via concurrency_limit_per_user. A mod creator's usage limit is available via the Cloud Cooking User Cook Usage Object, which explains both concurrency_limit_per_user and concurrency_used (the number of cooks the user currently has pending or actively running).

When a creator is at their concurrency limit, new submissions are blocked until their existing cook jobs are complete.