Redeploy, deploy a new image, or roll back?

Several actions can create a new deployment attempt. They do not all select the same image or solve the same problem. First decide whether you want to apply configuration, choose a different image or return to a historical artifact. This distinction matters most when application settings contain an image that differs from the version currently running.

Use Redeploy current version when you want to apply updated environment configuration while keeping the exact active image. Saving environment values alone does not deploy them.

For example, your active image is A and your saved image is B. You update an environment variable, save it and redeploy the current version. The selected artifact remains A, accompanied by the updated configuration.

Use Deploy saved image when the image in your application settings is the one you deliberately want to deploy next. In the previous example, this action selects B instead of preserving A. Review the image reference and the application’s current configuration together. Once the request is accepted, follow the attempt’s outcome before treating the new version as active — a deployment request can be accepted while the runtime is still starting.

Rollback explicitly selects an eligible successful artifact from deployment history. In iDeployed, artifact rollback retains current environment and application configuration. That means rollback is not a complete time machine for every setting: an older application artifact will run with the current configuration, and rolling back an image does not restore a database or old environment values. Check that the selected historical version can use those current values before requesting it.

Deployment history shows individual attempts and their outcomes. Runtime logs show application behavior. Build output describes another stage: producing the container image. Use these views together. Identify the active artifact, inspect the relevant attempt and verify the result after your action. A failed attempt and a healthy active version can coexist; the latest attempt alone is not the full application state.