Known limitations

• Check the release notes for published images and supported versions.

• The public API reference covers supported integration endpoints. Additional endpoints used by the web UI are internal and are not part of the public contract.

• Remote workload backups and restores through regular Agents, Edge Agents, or Swarm Node Agents require S3-compatible storage. Filesystem repositories are supported for control-plane backups and Local-connector workloads; see backup repositories.

• The backup policy form offers Stop attached containers, but the current execution path does not stop or restart workload containers. Use Live and prepare application-consistent data separately; see backup consistency.

• Script editor completions include shortcuts that the runtime does not expose. Use generated operation names through citadel.api; see script globals.

• Remote builds create a Git tar archive with a 12 MiB output limit before Agent transfer. That archive step does not apply .dockerignore, and the Dockerfile must be inside the selected context; see build context size.

• Citadel supports Task logs, terminal sessions, volume browsing, and container statistics across Swarm Nodes. For Nodes beyond the connected manager, enable Cluster node coverage using Install node agents on the Platform page. Saving a Platform does not install node agents automatically.

• Swarm Node Agent installation can reject custom OCI images whose registry metadata does not identify supported hardware. Use a published Agent image or publish the custom image as an index with accurate platform entries.

• Swarm Config and Secret payloads are immutable after creation. Citadel can update supported metadata, while payload rotation requires a replacement and workload update.

• Docker Swarm rejects Compose fields it cannot represent. Citadel preflight reports blockers before native Stack deployment.

• The Stack binding editor exposes Mounted file, but the current Rust deployment path does not deliver those secret bindings. Use environment-variable bindings or separately configured Compose secrets; see secret delivery modes.

• Git Stack rollback reloads saved configuration but does not automatically pin an unpinned branch to the release's recorded deployed commit. Explicitly select the earlier commit when exact source recovery is required; see Git rollback.

• Swarm Stack rollback does not restore recorded Docker Secret or Config versions or automatically retain those versions for rollback. Preserve required resources before redeploying an earlier configuration.

• Rolling Swarm updates retain historical Task containers according to Docker behavior; Citadel may hide those from current workload summaries and can prune eligible historical containers according to platform policy.

• Restoring a previous Core image does not automatically reverse database migrations.

• Git Stacks materialize the full committed tree within 512 entries/files and 12 MiB on Core across all connectors; generated ownership files also consume the Agent's final transport budget. See Git source requirements.

• Git repository hooks run trusted shell commands on Core without a sandbox. They do not provide exactly-once execution or add uncommitted generated files to Git Stack inputs. Failed syncs with hooks require review and manual retry. See repository hooks.

• Build Pool execution supports self-managed inbound and Edge Agents. AWS EC2 provisioning is not implemented; manually provisioned AWS VMs can be self-managed builders.

Release notes may add narrower limitations for a specific version. Treat those notes as authoritative for that release.