Discloud Paid plan resource limits configuration in discloud.config

Question

Determine whether the Discloud Paid plan allows users to override the default CPU and RAM allocations by specifying custom values in the discloud.config file.

The platform documentation states that resource limits are strictly enforced based on the selected plan, but it does not clarify if the configuration file can be used to request different limits or whether such entries are ignored or cause deployment failures. This uncertainty affects capacity planning for bot workloads that may need more resources than the plan’s default allocation.

Does Discloud ignore custom resource definitions in discloud.config for Paid plans?
If ignored, what is the correct procedure to request higher limits on a Paid plan?
Are there any supported fields in discloud.config for specifying CPU or RAM overrides?

Tasadduq Burney · Answer

Direct answerThere is no confirmed discloud.config field for overriding CPU or RAM on a Discloud Paid plan. Do not add invented fields such as cpu, ram, or memory expecting them to change your allocation; they may be silently ignored or cause deployment validation errors. Resource limits appear to be tied to the selected plan, not the configuration file.Confirmed facts versus unconfirmed behaviorItemStatusNotesCPU or RAM override fields in discloud.configNot confirmedNo authoritative schema reference confirms these fields for Paid plans.Effect of custom resource entriesUnconfirmedLikely ignored or treated as invalid, but this is not verified from current documentation.Typical scope of discloud.configEstablished patternGenerally associated with entry point, startup command, and environment settings rather than plan entitlements.Path to higher limitsLikely, unconfirmedSelect a higher paid tier or request changes through the dashboard or support.Steps for this caseOpen the Discloud dashboard and note the CPU/RAM allocation listed for your current Paid plan.Review your project’s discloud.config and remove any custom CPU or RAM fields you added.If your workload needs more than the plan shows, either upgrade to a higher paid tier or contact Discloud support to ask whether a limit increase is available.Optionally, deploy a test bot with a candidate override field and inspect the deployment logs to see whether the platform accepts, ignores, or rejects it. Treat any observed behavior as specific to your account and platform version.Assumptions and uncertaintyThis answer assumes you are using the current Discloud Paid plan experience. Platform schemas and plan allocations can change, and this response does not include a live check of Discloud documentation. Because the available research flags current verification requirements, treat this as a conservative draft for human review until you confirm the behavior in your own dashboard or with Discloud support.Missing diagnostic detailProvide the exact name of your current Paid plan. This determines whether upgrading to a higher tier is possible or whether you must contact support for a limit exception.

Discloud Paid plan resource limits configuration in discloud.config

1 answer

Direct answer

Confirmed facts versus unconfirmed behavior

Steps for this case

Assumptions and uncertainty

Missing diagnostic detail

Your perspective belongs here.

0 question comments

Item	Status	Notes
CPU or RAM override fields in `discloud.config`	Not confirmed	No authoritative schema reference confirms these fields for Paid plans.
Effect of custom resource entries	Unconfirmed	Likely ignored or treated as invalid, but this is not verified from current documentation.
Typical scope of `discloud.config`	Established pattern	Generally associated with entry point, startup command, and environment settings rather than plan entitlements.
Path to higher limits	Likely, unconfirmed	Select a higher paid tier or request changes through the dashboard or support.