Container app jobs execution history

Hi @Andrii Zahorodniuk ,

When job executions keep triggering daily but the Execution history stops updating (and the last entry is stuck across multiple jobs/subscriptions), it usually points to something off with how/where execution history is being recorded/displayed, rather than the scheduler itself.

Here are the few things to check:

1. Confirm execution history via the supported API/CLI (not only the portal UI)

Jobs maintain a recent execution history that you can retrieve using supported interfaces.

• Azure CLI: list job executions

az containerapp job execution list \

 --name "<my-job>" \

 --resource-group "<my-resource-group>"

• Azure Resource Manager (REST): get job executions

GET https://management.azure.com/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RESOURCE_GROUP>/providers/Microsoft.App/jobs/<JOB_NAME>/executions?api-version=2023-05-01

If the portal is stale, the CLI/REST output can help determine whether the executions are truly missing from the execution-history store, or if it’s just a display issue.

2. Remember the execution history is limited (last 100 successful+failed)

For scheduled and event-based jobs, execution history is limited to the most recent 100 successful and failed executions.

So if you have a high-frequency job (or multiple rapid executions due to retries), the history could roll over and appear “stopped” depending on what you’re looking at.

Even so, since you’re saying jobs run once per day, this should generally still advance—so it’s worth confirming with the CLI/REST above.

3. Cross-check using the logs provider (this is the “source of truth” for runs)

Execution history can be queried, but for deeper verification, query the logs configured for the Container Apps environment.

The docs provide a sample Log Analytics query pattern for job logs (default provider example):

let job = "<myjob>";

ContainerAppConsoleLogs_CL

| where ContainerJobName_s =~ job

| project TimeGenerated, Log_s, ContainerGroupName_s, EnvironmentName_s

| order by TimeGenerated asc

If your logs show the daily runs continuing past 2026-05-31, that strongly suggests:

• the job executions are still happening, and
• the execution-history reporting is what’s failing to surface.

Hi. Yes, I undeerstand. Job is running both on schedule and I trieed to run it manually. It works. Execution history is stale using programmatic access and on ui on different jobs across multiple subscriptions @Pravallika KV

On one occasion though one of the jobs I was triggering manually recorded 1 attempt among like 10 of them. so couple of jobs are silent after 05-31. and one of them has 1 more record in history 06-11(todays date)

Hi @Andrii Zahorodniuk , I've reached out to you over private message, please check and respond.

@Pravallika KV We are also experiencing the same issue and it started at the same time, we no longer see executed jobs. If we remove/rebuild the resource it starts showing, but after a while it stops again. Any progress in the private messaging with the original poster? I found at least one more post with the same problem:
https://learn.microsoft.com/en-us/answers/questions/5918667/azure-container-app-job-not-showing-recent-executi