Execution Jobs

Whenever DeployClear interacts with your infrastructure, it creates a Job. A Job represents a single lifecycle event within a Cloudflare Container, such as a Plan, an Apply, or a Destroy.

Jobs are completely distinct from Requests. A single Request typically consists of two Jobs: the initial Plan job, and the subsequent Apply job (if approved).

The Job Lifecycle

When a Job is dispatched by DeployClear:

1. It enters the queued state while it waits for a Cloudflare Container instance to spin up.
2. It transitions to running. The container executes the Terraform binary.
3. As terraform writes to stdout/stderr, those logs are streamed seamlessly back to DeployClear via WebSockets, allowing you to watch the run live.
4. The Job concludes as either completed or failed depending on the exit code of the Terraform binary.

Viewing Jobs

To debug a failing pipeline or view historical output:

1. Navigate to the Jobs page in the left sidebar.
2. You will see a comprehensive list of all executions within your Team workspace.
3. Click on any Job ID to open the Logs Viewer.

The Logs Viewer

The Logs Viewer acts essentially as a terminal capture. It retains the exact stdout and stderr emitted by Terraform.

If a deployment fails, the Logs Viewer is your first line of defense. Because DeployClear runs isolated ephemeral containers, you eliminate the variable of local machine configuration entirely. If it fails in DeployClear, it is definitively an issue with the Terraform configuration, the provider limits, or an invalid Secret.

Next: Analyzing the Audit Log →