# Mission version history

Sydekyks user and operator guide. Check feature availability and release-specific installation requirements.

Sydekyks keeps the distinction between the draft you edit and the published configuration used by live triggers.

## ​How versions work

- Edit the mission in draft form.

- Publish the draft when it is ready.

- The published version becomes a fixed configuration.

- Editing again creates a new draft when one does not already exist.

Open the builder’s version/history control to inspect earlier versions. If you restore an earlier configuration into a draft, review and test it before publishing. App credentials, destinations and provider behavior may have changed since that version was first used.

## ​Before restoring

Compare trigger settings, step inputs and account references with the current version. Decide whether the older behavior would repeat work already completed by the newer mission.

Version history changes the mission configuration. It does not undo emails, record changes or other effects from previous runs. Managed project environments and Git Sync are separate optional controls and are excluded from this guide.