Versions
Understand publish builds, active releases, and rollback
Every publish creates an immutable Version for the Experience. A Version records the Project snapshot, delivery configuration, and build that produced one signed native-runtime release.
Version lifecycle
- Publish creates the next Version number and queues its build.
- The build compiles and packages the Journey release.
- The release is signed and its artifact identity is recorded.
- A successful build becomes Ready.
- The selected ready Version can become the Experience’s live Version.
Each publish creates a new Version even when it updates an existing Experience. Editing the source Project does not mutate prior Versions.
Build status
| Status | Meaning |
|---|---|
| Building | Work is queued or running; the Version cannot be activated yet. |
| Ready | The signed release built successfully and can be made live. |
| Failed | The release was not produced. Read the publish error, fix the Project or target, and publish again. |
The Versions tab marks the active Version with Live. A failed or still-building Version has no activation action.
Activate or roll back
To switch to an existing ready Version:
- Open the Experience and choose Versions.
- Open the menu for a ready Version that is not live.
- Choose Make Live.
Activation changes the Version delivered for that Experience; it does not create another Version. Use it to return to a known-good release while you repair the source Project.
Safety during an update
The prior live Version remains the delivery authority while an update builds. Only a successful, eligible Version can replace it. If a build fails, users continue receiving the prior live Version.
The SDK also authenticates each selected release before presentation. Build success alone cannot make an altered or incomplete release render on a device.