Skip to main content
This article explains how Draft and Published states apply to each deployed version of a Flows custom app, and how the active version determines what users see on the Custom apps page in Cognite Data Fusion (CDF). Every version of a Flows custom app has a lifecycle state that controls whether it can be modified. Separately, an app has at most one active version — the build users run when they open the app from Custom apps.

​
Version states

Each app version is always in one of two states — Draft or Published. The state controls whether you can change its files and how you promote that build for users.

​
Draft

A version starts as Draft after you run apps deploy. Draft versions:
  • Are mutable — you can redeploy to update files, change the entry point, or iterate freely.
  • Can be shared via a direct link.
  • Are not the active version until you explicitly activate them.
A draft application does not require application certification. On production projects without Dev status, Cognite’s app certification signature (.cert.sig) is required only when you publish.

​
Published

To transition a version from Draft to Published, run apps publish. Published versions:
  • Are immutable — files and configuration are locked and cannot be changed.
  • Can be shared via a direct link.
  • Can be set as the active version for the app.
The transition from Draft to Published is irreversible. To make changes, deploy a new version. Signature requirements for publish are covered under CLI commands.

​
Active version

An app has zero or one active version at any time. If no version is active, the app does not appear on the Custom apps page in CDF. Once you activate a version:
  • The app becomes visible on the Custom apps page, and the activated version is what users open.
  • It is the version served when no specific version is requested in the URL.
Setting a version as active automatically replaces the previous active version. Rollback is instant — activating any previously published version takes effect immediately with no file operations.

​
CLI commands

apps activate combines publish and activate in one step. Use it when you’re ready to ship directly without a separate review.
Publishing requires a developer signature on every project, including those with Dev status. Production projects without Dev status need both that signature and Cognite’s app certification signature (.cert.sig) from application certification. See Code signing.

​
Typical workflow

Dev status (developer signature only):
Production without Dev status (developer signature and Cognite’s app certification signature):
To ship directly without a separate review step, use apps activate after the required signatures are in place (deploy > sign > activate on Dev status, or deploy > sign > application certification > activate on production). See Application certification and Code signing.

​
Further reading

Last modified on August 20, 2026