Deletion requires Operator or Admin access. Before deleting, identify callers, domain routes, scheduled work, and data that must be retained.
Delete
- Record the image, required settings, and storage location if recovery may be needed.
- Stop or redirect clients that depend on the application.
- Review attached XHealth checks, XJob tasks, and Guardian activity.
- Confirm deletion in the application page.
- Verify that the application disappears and its tasks finish exiting.
Application deletion removes its associated checks, jobs, and release-validation resources. Container exit is asynchronous, so related network resources can remain in use briefly.
What remains
Business data volumes remain on their original servers. Groups remain until separately deleted. External DNS records and third-party resources are not automatically removed.
If data is no longer needed, delete its volume through volume management after checking backups and references. Do not interpret an absent application as proof that a volume is empty.
Recovery and troubleshooting
Recreating the same name creates a new application identity; it is not an undo operation or a restoration of the previous definition. Reconstruct configuration from your records and verify the appropriate existing volume before starting a stateful service.
If group deletion reports that it is busy immediately afterward, wait for tasks to exit and inspect remaining network references. See groups.
For an unsuccessful release, consider rollback before deleting the application.