Execution History
The Execution History section provides a complete record of all workflow runs, including their status, trigger details, and analytics.
Executing a Workflow
- Navigate to the Workflow Details page for the workflow you want to execute.
- Ensure the target environment in the Deploy stage is active.
- Click Update & Execute Now in the top-right corner.
Atmosly will validate your workflow configuration, save any pending changes, and begin execution.
If the workflow has an automatic trigger configured, it will also execute automatically when a matching code push is detected via webhook.
Execution Process
When a workflow executes, the following stages run sequentially:
| Phase | Description |
|---|---|
| Validation | Verifies that all workflow stages are correctly configured and the target environment is active. |
| Source | Clones the repository and checks out the configured branch (or fetches the container registry image). |
| Pre-Build Tools | Runs configured pre-build tools (detect-secrets, custom scripts) if enabled. |
| Build | Builds the Docker image using the specified Dockerfile, build context, and platform. |
| Post-Build Tools | Runs configured post-build tools (Trivy scan, SonarQube, custom scripts) if enabled. |
| Push | Pushes the built image to the configured container registry. |
| Post-Push Tools | Runs configured post-push custom scripts if enabled. |
| Deploy | Deploys the image to each target environment sequentially. Manual environments wait for approval. |
| Post-Deploy Tools | Runs configured post-deploy scripts if enabled. |
Viewing Execution History
You can access execution history from two locations:
Via Workflow Builder
- Open the workflow in the Workflow Builder.
- Select the Execution History tab.
Via Pipelines Module
- Navigate to Pipelines from the left menu.
- Select the relevant pipeline to view its execution history.
Execution List
Each execution entry displays:
| Column | Description |
|---|---|
| Execution ID | Unique identifier for the execution. Click to view detailed logs. |
| Triggered At | When the execution was initiated. |
| Triggered By | The user or system event (webhook) that triggered the execution. |
| Status | Current execution status (see table below). |
| Report | Link to download security/quality scan reports from this execution. |
Execution Statuses
| Status | Description |
|---|---|
| Pending | The execution is queued and waiting to start. |
| Running | The pipeline stages are actively executing. |
| Succeeded | All stages completed successfully. |
| Failed | One or more stages failed. |
| Error | An unexpected error occurred during execution. |
| Deployment Pending | CI stages completed. The deployment is waiting to be triggered (manual deploy type). |
| Approval Pending | The deployment requires approval from designated approvers. |
| Approval Rejected | An approver rejected the deployment. |
| Terminating | A user initiated termination of the running workflow. |
| Terminated | The workflow was successfully terminated. |
| Termination Failed | The termination request failed. |
Execution Analytics
The Execution History section includes an analytics chart showing execution trends over time:
- Time Filters — Filter by 7 days, 14 days, 30 days, or by month (1–12 months).
- Status Breakdown — The chart displays separate lines for each status (Succeeded, Failed, Running, Pending, Approval Pending, Terminated, etc.).
- Totals — View the total number of executions per time period.
Terminating a Workflow
To terminate a running workflow:
- Navigate to the execution that is currently Running.
- Click the Terminate button.
- Confirm the termination.
The workflow status will transition to Terminating and then to Terminated once the underlying Argo Workflow is successfully stopped. If termination fails, the status will show Termination Failed.
Terminating a workflow stops all running pipeline stages immediately. Any in-progress builds or deployments will be cancelled. This action cannot be undone.
Execution Logs
Click on an Execution ID to view detailed logs for each pipeline stage. Logs are streamed in real-time during active executions and stored for completed runs.
| Feature | Description |
|---|---|
| Stage-by-Stage Logs | View logs for each individual stage (Source, Build, Push, Deploy, Tools). |
| Real-Time Streaming | Logs update in real-time while the execution is running. |
| Log Storage | Completed execution logs are stored and accessible from the execution history. |