conflicting_changes
HTTP 422 Only one resource change per request
What happened
You asked for more than one resource change in a single server update, or combined a name change with one of them. Cores and memory together count as one change; the plan and the disk size are each another, and only one of the three may travel per request. Each change occupies the server while it is applied, so the second would be refused after the first had already taken effect.
What to do
Split the update into separate requests and send them one at a time, waiting for each task to finish before the next. Rename the server in its own request.
Retrying
Fix the request and send it again.
How it arrives
{
"type": "https://docs.fiberax.com/errors/conflicting_changes",
"title": "Only one resource change per request",
"status": 422,
"code": "conflicting_changes",
"request_id": "a277dcd1ca652c65"
}
Branch your code on code, never on the wording of title.