Deployments tab overview

Use the Deployments tab on a Service to see history, logs, and the primary ship actions. Redeploy is how you roll forward after config or code changes. Rollback in dFlow means getting back to a known-good release (Git commit, image tag, or data restore), then shipping again, not a separate magic undo button on each row.

Prerequisites

• You can open the Application → Environment → Service in the dashboard.
• The Service is attached to compute (a Worker Node) for that Environment.

Deploy and redeploy

1. Open the Service.
2. Open the Deployments tab. The heading is Deployments, with a short description: deployment history and status.
3. Use the Deploy or Redeploy control beside that heading (rocket icon).
   • Before the first successful deployment, the button is Deploy.
   • After a successful deployment, it becomes Redeploy.
4. If you chose Redeploy, a Redeployment dialog opens. Pick one option:
   • Without cache: rebuild or pull a fresh image (full rebuild path).
   • Use existing cache: reuse the existing Docker image for a faster path.
5. Confirm with Redeploy (or deploy without the dialog on first deploy).

Expected outcome: A new row appears in the deployment list with a status badge. Noisy failures usually surface in View Logs on that row (see Logs).

Restart and stop (runtime)

Beside Deploy / Redeploy, the same action area includes:

• Restart: re-runs the Service without necessarily rebuilding. You must have at least one deployment first; otherwise the product prompts you to deploy.
• Stop: stops the Service. For database Services that are Exposed publicly, the UI asks you to Unexpose before stopping.

These actions are queued; toasts often say work was Added to queue.

Roll back application code (Git App Services)

There is no per-deployment “rollback” button in the list. To return to older application code:

1. In your Git provider, identify the commit or branch you trust.
2. In the Service Overview tab, set the branch (or equivalent) to that commit or branch, Save, then Redeploy with the cache option that matches whether you need a clean build (Without cache) or a faster rollout (Use existing cache) according to your change.

Roll back container images (Docker Services)

Point the Service at the previous image tag or digest your registry still hosts, Save, then Redeploy (usually Without cache if the platform must pull a different image).

Roll back data (database Services)

Use Backups to restore from a snapshot instead of trying to “redeploy” data.

Screenshots

Recommended captures (staging or sanitized data), per the documentation screenshot policy:

• Deployments tab showing the heading, Deploy / Redeploy, Restart, and Stop.
• Redeployment dialog with Without cache and Use existing cache selected alternately.
• A deployment row with View Logs visible.

Related

• Deployments
• Logs
• Deployment issues
• Logs and debugging