Skip to main content
A Run is a single execution of a Deployment — whether that is an execute (deploy) or a destroy operation. Every Run is tracked, logged, and stored so you have a complete history of every change made to your infrastructure. This guide explains how to track progress, read logs, and respond to failures.

​
Finding Runs

​
From a Deployment

  1. Open the Deployment detail page
  2. The Runs section shows a list of all runs for this deployment
  3. Each run entry shows:
    • The run type (Execute or Destroy)
    • The current or final status
    • When it was triggered
    • Who triggered it
Click on any run to open the Run detail page.

​
From a Pipeline

If a deployment was triggered as part of a Pipeline, you can also find its run from the Pipeline Run detail page, which lists all individual deployment runs within that pipeline execution.

​
Run Status at a Glance

The status badge on the Run shows where it is in its lifecycle: See Deployment Statuses for a complete reference.

​
Viewing the Execution Log

When a run is in progress or has completed, the execution log is available from the Run detail page. The log shows:
  • Each step of the execution process in real time (while the run is active)
  • Confirmation of each resource created, modified, or deleted
  • Any warnings or informational messages
  • The full error message and stack trace if the run failed
The log streams live while the run is in the Applying or Destroying state. You do not need to refresh the page — it updates automatically.

​
Viewing Outputs

After a successful run, some templates produce outputs — values generated by the infrastructure that are useful for connecting applications or other systems. Common examples:
  • The endpoint URL of a provisioned web service
  • The connection string for a provisioned database
  • The IP address of a virtual machine
  • The ARN or resource ID of a cloud resource
Outputs are shown in the Outputs section of the Run detail page. Copy these values and share them with your team as needed.

​
What To Do When a Run Fails

If a run reaches the Failed state: Step 1: Read the error message The Run detail page shows a clear error summary at the top. Read it carefully — it usually explains what went wrong (e.g., “Insufficient IAM permissions”, “Resource already exists”, “Invalid variable value”). Step 2: Check the execution log Scroll through the log to find the exact point of failure. The log typically shows which resource failed and why. Step 3: Fix the underlying issue Common causes of failure:
  • Wrong variable values — edit the deployment and correct the values
  • Insufficient permissions — contact your cloud administrator to add the necessary permissions to the cloud integration
  • Resource naming conflict — a resource with the same name already exists; use a unique name
  • Quota exceeded — your cloud account has reached a limit; request a quota increase from your cloud provider
Step 4: Re-execute the deployment After fixing the issue, return to the Deployment detail page and click Execute again. Amnify Deploy will generate a new plan that accounts for any resources already created in previous partial runs — you will not end up with duplicates.

​
Cancelling an In-Progress Run

You can cancel a run at the approval steps (Awaiting Plan Approval and Awaiting Apply Approval) by clicking Cancel. See the Approval Workflow guide for details. Once a run enters Applying or Destroying, it cannot be cancelled — the cloud changes are in progress.

​
Run History

All runs are permanently stored in the Run history of each Deployment. There is no automatic cleanup — you can always go back and review the log, outputs, or plan of any past run. The run history is useful for:
  • Understanding what changed and when
  • Auditing who triggered each change
  • Debugging issues by comparing a successful run with a failed one

​
Next Steps