Restart Site

  • Updated

Use Mission Control to restart the target Optimizely Configured Commerce instance. The restart action only restarts the Configured Commerce and integration applications; it does not restart Spire or the CMS application.

Configured Commerce uses a rolling deploy strategy for its environments, ensuring there are always containers available to the load balancer. This means that even during a restart, websites should be fully available to customers.

Steps

  1. Log in to Mission Control.
  2. Go to Customers and select a customer.
  3. Select a target Configured Commerce instance.
  4. Click Actions on the instance page and select Restart Site.
  5. (Optional) Schedule the action by toggling Scheduled Execution to On and selecting a time and date.
  6. Review the details to confirm the selected instance (and scheduled time, if selected). You can ignore any greyed-out or immutable fields because they are for development or debugging.
  7. Click Continue. If scheduled, the action runs at the specified time. Otherwise, the action runs immediately. This begins to restart Configured Commerce and integration deployments and continuously polls for the restart status for about an hour.

  8. Wait until the status is marked as Complete on the Action Request page.

    If the restart takes over an hour, the action stops checking the restart status and exits. At this point, the action status shows Failed. Submit a ticket with Optimizely Support with a link to the failed action request page.

Example scenarios

  • Changing settings. Several settings require a site restart. When you change a setting, the Admin Console provides an alert if that setting requires a restart. Examples include search provider, storage provider, or site timeout.
  • Stopping hanging/frozen integration jobs.
  • Making a plugin (RTP/RTI/etc.) show in settings.
  • Making a new connection show in the internal WIS.