View the historical optimiser configuration for an occurrence
Open a past service occurrence and review the optimiser configuration that was attached to that service at the time. The historical view is read-only, so operators can audit settings even if the current configuration was later changed or archived.
In this article
Historical optimiser review starts from the occurrence, not from the current settings list. Use it when an operations user needs to verify which capacity rules applied to a past Harbor Soho service.
The lookup is tied to occurrence_id. Without that occurrence context, the same configuration detail route returns the current configuration instead of the historical audit view.
Before you start
- You are signed in to Harbor Demo Group with access to Harbor Soho or the relevant location.
- The occurrence is a past service occurrence for the selected location.
- The occurrence or its parent service resolves the requested optimization_config_id.
- Your account has optimisation view access. If entering from the reservation occurrence detail, your account also has reservation occurrence view access.
Instructions
- 1.
Open the past occurrence
From Reservations, open the detail page for the past service occurrence you want to audit, such as a previous Soho lunch service at Harbor Soho.
- 2.
Choose the optimiser action
Open the occurrence actions and choose the optimiser configuration action. In the current app this label appears as Configuracion del optimizador.
- 3.
Review the read-only settings
The optimiser configuration form opens with the historical name, description, default flag and settings. Review the values as audit evidence; this view is not for editing.
- 4.
Return to the occurrence
Use Cancel or back navigation when the review is complete. The historical route forces read-only mode, so Save remains blocked even for users who can manage optimiser settings.
Validations and limits
- The app resolves optimization_config_id from the occurrence payload before checking the parent service event payload.
- The historical request includes occurrence_id only when the configuration screen is opened in read-only mode.
- The requested configId must match the optimiser configuration resolved by the occurrence or service event.
- The occurrence must belong to the route locationId and must be strictly before today in the service timezone.
- If the referenced configuration was soft-deleted after the service, the historical lookup can still return the archived snapshot when it remains within the readable scope.
Expected result
The operator can prove which optimiser configuration applied to the past occurrence without creating, editing or deleting configuration data.