Delete an optimisation configuration with replacement
Archive a non-default optimisation configuration in the current organisation or location. If services use it, Antylogic asks for a second confirmation, moves active references to the applicable default configuration, and keeps historical context where required.
In this article
Use this guide when Harbor Soho or another location needs to retire an editable optimisation configuration without breaking services that already reference it.
The deletion is intentionally cautious: default, inherited, system, and out-of-scope configurations cannot be removed from the current screen, and assigned services require an explicit replacement confirmation before Antylogic archives the configuration.
Before you start
- You are signed in with an organisation context; for a location-level configuration, a location such as Harbor Soho is selected.
- You have `optimization:manage` permission. Users with only `optimization:view` can inspect configurations but cannot delete them.
- The configuration is active, editable in the current scope, and is not marked as the default.
- Another default optimisation configuration exists in the same applicable scope: the same location for location configurations, or the organisation for organisation configurations.
- If the configuration is assigned to services, you are ready to approve the second replacement confirmation after Antylogic shows the affected service count and default replacement.
Instructions
- 1.
Open the optimiser configuration list
In Harbor Soho, open Reservations > Optimiser and find the non-default configuration in the Optimisation configurations table. Organisation-level configurations are managed from the organisation optimisation configuration page and follow the same scope rules.
- 2.
Start deletion from the row action
Open the row menu and choose Delete. Antylogic opens Delete configuration and names the selected configuration. Confirming this first prompt requests deletion, but it does not yet authorise service replacement.
- 3.
Review the replacement impact
If services use the configuration, Antylogic changes the modal to Replace and delete configuration. Review the affected service and location count and the default configuration that will replace it. Operators cannot choose a different replacement in this flow.
- 4.
Confirm the archive
Choose Replace and delete. Antylogic replaces active and future service references with the applicable default configuration, preserves historical configuration references where needed, archives the deleted configuration, refreshes the list, and shows the deletion result.
Validations and limits
- The Delete action is available only for rows editable in the current scope.
- Default optimisation configurations cannot be deleted.
- Inherited, system, or out-of-scope configurations may be visible but cannot be deleted from the current screen.
- If services reference the configuration, the first delete attempt must return a replacement confirmation before any replacement is applied.
- The replacement is always the applicable default configuration calculated by Antylogic; this flow has no manual replacement selector.
- If no alternative default exists in the required scope, deletion is blocked and service references are not changed.
- Any `confirm_replacement` value other than `true` is treated as not confirmed.
- A successful deletion returns `204 No Content`, and normal lists no longer show the archived configuration.
Expected result
The non-default configuration is archived, active service references use the applicable default configuration, and historical service data remains traceable through preserved references or snapshots when required.