Managing experience status in Sitecore Personalize

The status of an experience determines whether the experience can be edited, paused, set to production, and more. The experience status also determines what appears in the QA tool and analytics.

You can see the status of the experience at all times beneath the name of the experience on the given screen. The experience status can be any of the following:

Draft - When an experience is initially created, Sitecore Personalize automatically assigns it a draft status. You can edit an experience with this status. An experience with a draft status can change to publishing or completed.
Publishing - An experience has a publishing status only for a number of minutes. This occurs when you click the Start button on the status banner. Sitecore Personalize compiles the code and deploys it to the Content Development Network (CDN) to make it available in production. This is true whether you set the experience to Run Now or Scheduled. The publishing status typically takes a number of minutes to complete. You can't manually move an experience with a publishing status to another status. Sitecore Personalize automates the status change.

An experience with a publishing status can automatically change to:
- Scheduled: If the experience successfully deploys to the CDN and was set to Scheduled.
- Live: If the experience successfully deploys to the CDN and it was set to Run Now .
- Draft: If the experience fails to deploy to the CDN and the experience had a previous status of draft.
- Paused: If the experience fails to deploy to the CDN and the experience had a previous status of paused.
Scheduled - An experience has a scheduled status if during the publishing status, it successfully deployed to the CDN. An experience with a scheduled status can automatically change to live if the current date/time is within the scheduled range of the experience .

An experience with a scheduled status can change to paused.
Live - When your experience has a status of live, it means that personalization is now in effect.

An experience has a live status if it successfully deployed to the CDN while in the publishing state, it was set to run now, or if it was in a scheduled state and the current date/time is within the scheduled range. An experience with a live status can change to:
- Paused: If you click the Pause button.
- Completed: If the experience was in a scheduled state and the current date/time is no longer within the scheduled range, or if a user clicked the Complete button.
Paused - An experience has a paused status if you clicked the Pause button while the experience was scheduled or live.

You can edit an experience with the paused status, but it will invalidate your test results.

An experience with a paused status can change to publishing if you click the Start button, or completed if you click Complete.

Note

To pause an experience, from the respective Build summary screen, click the Pause button. The Pause Experience confirmation window displays. Click the Pause button. The experience is paused.
Completed - An experience has a completed status if the experience was in a scheduled state and the current date/time is no longer within the scheduled range or if a user clicked the Complete button when the experience had a paused status.

Do you have some feedback for us?

If you have suggestions for improving this article,