corestack_ company_ auto_ upgrades_ set
Turn automatic upgrades on or off.
When to use it
Turn automatic upgrades on or off for your company, or change the monthly limit. While they are on, a new site or environment that would take a CoreCluster past 90 % of its package first gets the smallest add-on raise that makes room (more cores, RAM or disk), or the next package, bought and added to the monthly bill, and the create goes ahead. A copy into an environment (never production) that is too small for it gives that environment a larger size first, the same way. Read corestack_company_auto_upgrades_get first.
Each upgrade stays on the monthly bill until it is changed back. The limit caps only what new automatic upgrades can add to the bill in one calendar month (UTC), and it starts again on the 1st: upgrades from earlier months stay on the bill and do not count towards it, so the bill can grow by up to the limit every month. A new site or environment created by anyone who can create them in the company's CoreClusters, including Corefinity staff working for the company, can lead to an upgrade.
Turning them on, or raising the limit, charges the company without asking each time. Before you send confirm_spend: true, show the person this agreement, word for word, with the limit, and send it only after they agreed:
I agree that automatic upgrades may be bought and added to our monthly bill without asking each time: CoreCluster add-ons (more cores, RAM or disk) or the next package when a new site or environment would not fit, and a larger size for a non-production environment that is too small for a copy into it. Each upgrade stays on the monthly bill until it is changed back. The limit caps what new automatic upgrades can add to the bill in one calendar month (UTC), and it starts again on the 1st. A new site or environment created by anyone who can create them in our CoreClusters, including Corefinity staff working for us, can lead to an upgrade.
Only the company's owners and billing contacts can do this. Turning them off, or lowering the limit, needs no confirm_spend. Takes no company: it is the token's company, so a token limited to some sites or clusters is pin_refused.
Ask for it
Using the Corefinity MCP server, call corestack_company_auto_upgrades_set with enabled true, monthly_limit 250. (Turn automatic upgrades on or off.) Tell me what it returned.Inputs
True once the person agreed to the agreement above. Needed to turn them on or raise the limit.
true to turn automatic upgrades on, false to turn them off.
The most that new automatic upgrades may add to the monthly bill in one calendar month (UTC), in the company's billing currency, two decimal places at most, from 1 up to max_monthly_limit (never above 100,000.00). Upgrades from earlier months stay on the bill and do not count towards it. Needed to turn them on.
Your assistant fills in a confirmation only after you agree.
Example call
{
"name": "corestack_company_auto_upgrades_set",
"arguments": {
"enabled": true,
"monthly_limit": 250,
"confirm_spend": true
}
}If it is refused
| Reason | What to do |
|---|---|
billing_forbidden | Only the company's owners and billing contacts can turn on automatic upgrades or raise the limit; anyone else without billing rights cannot change them at all. Ask an owner or billing contact. |
auto_upgrades_unavailable | Automatic upgrades cannot be turned on now (not available yet, billing in the Control Panel is not available for the company, or it has no billing account); the message says which. |
busy | An automatic upgrade is being made for the company right now; try again in a moment. |
invalid_arguments | On enabled (missing or not true / false), monthly_limit (missing when turning them on, below 1, above max_monthly_limit or more than two decimal places; the message gives the range, e.g. "Set a monthly limit from £1.00 to £100,000.00, in whole pence at most.") or confirm_spend (not true when turning them on or raising the limit); fields names the argument. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |