Skip to content

Job Execution History¶

Use this query to review Container Apps Job execution events, failures, retries, and timeout patterns.

Data Source¶

Table	Schema Note
`ContainerAppSystemLogs_CL`	Legacy schema. If empty, try `ContainerAppSystemLogs` (non-`_CL`).

Query Pipeline¶

flowchart LR
    A[Filter by job app name] --> B[Filter execution terms] --> C[Project run details] --> D[Sort by time]

Query¶

let JobName = "job-myapp";
ContainerAppSystemLogs_CL
| where JobName_s == JobName
| where Log_s has_any ("job", "execution", "retry", "timeout", "failed", "completed")
| project TimeGenerated, JobName_s, ExecutionName_s, Reason_s, Type_s, Log_s
| order by TimeGenerated desc

Example Output¶

TimeGenerated	JobName_s	ExecutionName_s	Reason_s	Type_s	Log_s
2026-04-04T12:54:30.462Z	job-myapp	job-myapp-6gx2m	Completed	Normal	Execution has successfully completed
2026-04-04T12:54:25.409Z	job-myapp	job-myapp-6gx2m	ContainerTerminated	Warning	Container terminated with exit code '0'
2026-04-04T12:54:23.569Z	job-myapp	job-myapp-6gx2m	ContainerStarted	Normal	Started container 'job-container'
2026-04-04T12:54:11.477Z	job-myapp	job-myapp-6gx2m	PulledImage	Normal	Successfully pulled image in 2.42s (58720256 bytes)
2026-04-04T12:53:55.549Z	job-myapp	job-myapp-6gx2m	SuccessfulCreate	Normal	Successfully created pod for Job Execution

Interpretation Notes¶

Group by time windows to identify retry storms.
Repeated timeout entries indicate timeout policy misalignment.
Normal pattern: predictable execution cadence and completion markers.

Limitations¶

Job detail depth can vary by trigger model.
Execution IDs may need CLI retrieval for full drill-down.

See Also¶