Skip to main content

Workflow Logs

The Workflow Logs section provides detailed logs for each workflow step, including the log type (such as source, build, and deploy), build number, duration, status (failed or succeeded), actions, and a "Logs" option that, when clicked, displays logs specific to the selected section.

Description of the image

Description of the image

  • Log Type: Whether it pertains to app CI or another process.
  • Build Number: Shows the unique number assigned to each build.
  • Duration: Displays how long the workflow step took to complete.
  • Timestamp: The exact time the logs were generated.
  • Log Details: A preview of the log entries, with color-coded lines indicating different statuses (e.g., errors in red).

Users can download the full log file for in-depth analysis by clicking on the "Download Report" link.

Reports​

Description of the image

The Reports section provides detailed summaries of each pipeline's execution, including:

  • Execution ID: A unique identifier for each pipeline run.
  • Triggered At: When the pipeline was triggered.
  • Trigger Type: Whether the trigger was manual, scheduled, or event-based.
  • Tool: The tool used during the stage (e.g., Trivy Scan).
  • Stage: The specific stage (e.g., Pre-Build).
  • Report Link: A downloadable link for the detailed report of the pipeline's execution.

Approving a Manual Step​

For pipelines that require manual approval at certain stages, you will see the step which requires Manual approval, from the Manual tag at the concerned stage. Click on 'Start' at the bottom of the card to continue the workflow.

For example, if the Source stage requires a manual approval, you will see 'Start Build' under the source stage. Click on the same to continue the workflow.

Description of the image

Troubleshooting​

Stuck Pipeline Detection​

If a pipeline stays in a Pending state for more than 5 minutes without progressing, Atmosly automatically shows a "Pipeline appears stuck" banner on the pipeline. This usually points to an issue with submission or scheduling rather than the build itself.

From the banner, click Diagnose Issue to open the debug view, which shows:

  • An automated diagnosis of the likely cause, with suggested next steps
  • The status of each step in the pipeline
  • How long the pipeline has been running (its age)

Marking a Pipeline as Failed​

If a pipeline is genuinely stuck and won't recover, use Mark as Failed from the debug view to stop waiting on it. This moves the pipeline into a failed state so you can re-trigger it or investigate further.

note

Atmosly also runs a background watchdog that automatically reconciles pipelines that stay stuck beyond a timeout, so a wedged pipeline won't stay pending indefinitely.

Still Stuck?​

If the problem persists, contact support at contact@atmosly.com with the pipeline's build number and details about the problem.