For AI agents: markdown of this page — /docs-content-en/changelog/infra-servers.md documentation index — /llms.txt
Change history: Servers
← Changelog. Entries: 111.
- 2026-10-01 NEW-1001-32: status change reason in the server activity feed
- 2026-09-30 FIX-0930-18: a busy server no longer points the machine field at a call that refuses
- 2026-09-30 BC-0930-29: a repeated galaxy server create no longer spawns applications
- 2026-09-30 NEW-0930-34: server activity feed
- 2026-09-28 BC-0928-12: server source access follows the owner key
- 2026-09-25 FIX-0925-4: a server whose creation failed on the cloud side no longer hangs in
PROVISIONING - 2026-09-24 NEW-0924-7: a default schedule for new machines
- 2026-09-24 FIX-0924-8: the run mode named at create now reaches a galaxy application
- 2026-09-23 FIX-0923-6: Reuse the application server after rebinding its key
- 2026-09-23 FIX-0923-8: galaxy app diagnostics now check the public address
- 2026-09-23 NEW-0923-12: server detail returns the last deploy's start command, install command and port
- 2026-09-22 BC-0922-9: Retrying an unfinished key rotation requires recovery
- 2026-09-21 NEW-0921-11: server deletion reports how the request to delete the machine in the cloud ended
- 2026-09-21 NEW-0921-12: DISK_FULL code in a server's provisionErrorCode after a failed repair
- 2026-09-20 FIX-0920-3: two simultaneous server creations for one application now yield one machine
- 2026-09-19 BC-0919-6: a project deploy key is issued only to an admitted Bitrix24 account
- 2026-09-18 BC-0918-2: A server development-team member gets their own key, and the key block gains the collaborator slot
- 2026-09-18 FIX-0918-5: the icon upload tells a permission refusal apart from a missing server
- 2026-09-18 NEW-0918-12: a server can be created already in the run mode you need
- 2026-09-17 NEW-0917-2: servers now report a run mode:
runModeandworkSchedulein reads - 2026-09-17 BC-0917-12: an empty query-parameter value in the operations list is no longer replaced by the default
- 2026-09-17 FIX-0917-14: on a busy server the machine-actionable recovery field names the guarded endpoint
- 2026-09-17 FIX-0917-19: Idempotency-Key protects galaxy app creation and reuse
- 2026-09-16 NEW-0916-4: server details show the port detected by the tunnel agent
- 2026-09-16 FIX-0916-7: API reports the effective tunnel state
- 2026-09-15 FIX-0915-10: external collaborator keys are bound to their server
- 2026-09-15 BC-0915-15: a read-only key can deploy an application to its own server again
- 2026-09-14 BC-0914-1: channel recovery may refuse to protect a running operation
- 2026-09-14 BC-0914-14:
Idempotency-Keyon server creation now has a 15-minute replay window - 2026-09-14 FIX-0914-18: the dedicated server card returns the installed runtime after a successful deploy
- 2026-09-10 NEW-0910-5: external membership is visible in V1: an external value for access.via and an externalServers block in /v1/me
- 2026-09-09 FIX-0909-8: the spec declares the 429 refusal of endpoints that carry their own rate limit
- 2026-09-08 NEW-0908-9: the standalone server auto-sleep policy is now visible through the API
- 2026-09-08 FIX-0908-11: the host from galaxyId is now available for reading
- 2026-09-04 FIX-0904-4: trial deployment hints account for galaxy host eligibility
- 2026-09-04 FIX-0904-5: a catalog card is no longer published without its Bitrix24 account binding
- 2026-09-03 FIX-0903-4: GET /v1/me no longer declares region as required
- 2026-09-02 NEW-0902-9: server creation answers 409
REISSUE_IN_PROGRESSwhile the application authorization key is being re-issued - 2026-09-01 FIX-0901-7: a transient image-registry outage no longer marks a galaxy app broken
- 2026-09-01 BC-0901-12: deleting a server now deletes the agent bound to it
- 2026-08-31 FIX-0831-1: a server whose agent never came up is no longer reported as running
- 2026-08-26 NEW-0826-5: creating an application from the Cowork/Code desktop — two new endpoints
- 2026-08-25 BC-0825-2: a read-only key no longer writes on platform endpoints
- 2026-08-25 BC-0825-10: Inline archive cap on the deploy body narrowed to 96 MB
- 2026-08-24 BC-0824-3: the deployment block changes shape for Belarusian accounts along with their access model
- 2026-08-24 NEW-0824-4: the Bitrix24 plan becomes the access condition for accounts licensed in Belarus
- 2026-08-24 FIX-0824-5: the server-creation hint in the key response no longer leads nowhere
- 2026-08-24 FIX-0824-6: the denial text for Kazakhstan and Uzbekistan no longer offers a subscription
- 2026-08-24 FIX-0824-13: an application on a galaxy host that does not boot can be deleted without a live tunnel
- 2026-08-24 FIX-0824-17: ACCOUNT_FROZEN is now documented on server creation
- 2026-08-23 NEW-0823-2: several employees can work on one application's code
- 2026-08-21 BC-0821-8: a busy shared galaxy exec channel now answers 409 instead of 502
- 2026-08-18 NEW-0818-10: applications catalog in the API: list and card
- 2026-08-17 FIX-0817-3: the Cowork/Code deploy-key mint now recovers a fleet stranded by earlier mints
- 2026-08-16 FIX-0816-4: the Cowork deploy-key handout no longer loses servers
- 2026-08-15 NEW-0815-4: an app can be added to the Bitrix24 catalog with a dedicated call
- 2026-08-14 FIX-0814-13: a wake schedule no longer shortens the auto-sleep you set
- 2026-08-14 NEW-0814-14: a write with a lossy-charset value now reports it
- 2026-08-13 NEW-0813-3: the real state of a sleeping galaxy app in the server GET and in the logs answer
- 2026-08-13 FIX-0813-9: deleting a galaxy app on a host that cannot be woken now answers a terminal 409
- 2026-08-13 FIX-0813-15: a server rename now shows up in the dashboard
- 2026-08-12 NEW-0812-3: The app port is pinned to the server and survives a wake
- 2026-08-11 NEW-0811-3: issuing a key with exactly the selected platform rights
- 2026-08-11 BC-0811-6: a server whose operating system does not boot answers with a dedicated code
- 2026-08-11 FIX-0811-25: galaxy app creation now reports that the provider, plan and region you sent were not applied
- 2026-08-10 NEW-0810-15: galaxy host disk usage is exposed in the server list
- 2026-08-07 NEW-0807-15: deploy now reports a displayName or description it did not apply
- 2026-08-06 BC-0806-9: V1: server status in JSON is always lowercase
- 2026-08-06 NEW-0806-10: deploying a galaxy app from a link or a saved version
- 2026-08-06 FIX-0806-17: base image registry unavailable during a galaxy app build is now transient, not fatal
- 2026-08-06 FIX-0806-25: a Galaxy Python build no longer fails on a version that exists
- 2026-08-05 NEW-0805-16: region is now optional when creating a server
- 2026-08-03 FIX-0803-3: server creation now says plainly when it returned the application's existing server
- 2026-08-03 NEW-0803-11: the one-shot galaxy app create now accepts
healthPath - 2026-08-03 FIX-0803-13: a galaxy app failure now names its actual cause in
provisionError - 2026-08-03 FIX-0803-15: a zip source archive no longer fails at extraction on a galaxy app
- 2026-08-02 BC-0802-2: self-hosted account access is no longer granted unconditionally
- 2026-07-30 FIX-0730-3: free tier no longer gets 402 PLAN_NOT_ALLOWED_ON_TRIAL when deploying into a galaxy
- 2026-07-30 BC-0730-6: a galaxy is no longer created on the free Bitrix24 plan
- 2026-07-29 FIX-0729-7: galaxy app deploy verifies reachability and returns steps
- 2026-07-27 NEW-0727-1: app favicon in one line — /_gw/icon
- 2026-07-27 NEW-0727-2: source-at-create: SOURCE_AT_CREATE_GALAXY_ONLY now carries a hint with a path to a galaxy
- 2026-07-23 NEW-0723-2: sources of a deleted server: access, cleanup, and an honest answer for purged bytes
- 2026-07-23 BC-0723-14: the /v1/me deployment.standalone.requiredFields.create shape is now an object + documents the name slug
- 2026-07-22 NEW-0722-2: scheduled wake (wake-schedules) is now available on every Bitrix24 account
- 2026-07-22 FIX-0722-5: the Bitrix24 plan probe no longer stops at a scope-limited developer key
- 2026-07-22 FIX-0722-6: the
regionfield in infrastructure responses always returns a region id - 2026-07-21 NEW-0721-3: Aggregated source registry — GET /v1/me/sources
- 2026-07-18 FIX-0718-1: deploy reuses the application's server instead of creating a duplicate
- 2026-07-17 NEW-0717-6: displayName and description on deploy set the Bitrix24 catalog card
- 2026-07-16 BC-0716-4: POST /v1/infra/servers rejects unknown body fields
- 2026-07-14 FIX-0714-11:
INVALID_JSON_BODYno longer quotes the engine parser text - 2026-07-14 FIX-0714-25: Aggregate enforces required filters; infra validation no longer leaks raw Zod
- 2026-07-14 NEW-0714-27: recover a stuck server exec channel
- 2026-07-14 NEW-0714-28: server description in
PATCH /v1/infra/servers/:id - 2026-07-13 FIX-0713-1: OAuth application key platform scopes now sync on create and edit
- 2026-07-13 FIX-0713-3: the reason for a failed first server provisioning is now visible
- 2026-07-13 NEW-0713-8: failed galaxy app builds now carry a
buildHint - 2026-07-11 FIX-0711-1: galaxies: GALAXY_HOST_UNREACHABLE is now actionable — structured hint and a precise provisionError
- 2026-07-10 NEW-0710-19: Idempotent server creation — Idempotency-Key header
- 2026-07-09 FIX-0709-1: transient DB overload now returns 503 with Retry-After instead of 500
- 2026-07-07 NEW-0707-6: error.hint on the 400 for a server create missing source and provider/plan/region
- 2026-07-07 FIX-0707-7: Galaxy deploy checklist in /v1/me now matches the actual contract
- 2026-07-02 FIX-0702-2: creating an app reuses a failed slot with the same name
- 2026-07-02 FIX-0702-20: infra: Cyrillic in displayName on application create
- 2026-06-25 FIX-0625-1: neutral provider, plan and region identifiers in the infrastructure API
- 2026-06-24 NEW-0624-4: placement and graduateFrom parameters on server create
- 2026-06-24 FIX-0624-5: server creation with code in source.content accepts archives up to 500 MB
- 2026-06-24 NEW-0624-11: provisionReason field in the server responses
- 2026-06-24 FIX-0624-12: the graduation signal fires for any galaxy app memory shortage
- 2026-06-23 FIX-0623-6: a deleted server returns 404 again