Azure Container App Job not showing recent execution history

Hi @Asa Xiao ,

Here are the key points an engineer can use publicly:

• Azure Container Apps Jobs keep a history of recent job executions, which you can view:
• in the Azure Portal (under your job’s Monitoring → Execution history), and
  • via Azure CLI using az containerapp job execution list, or
  • via ARM/REST using the job’s executions operation.
• The execution history shown in the portal for scheduled and event-based jobs is limited to the most recent 100 successful and failed job executions.

So, in normal conditions, the CLI/portal should still reflect the latest runs among the most recent executions (up to that limit), while the detailed logs/output are obtained from the logging provider configured for the Container Apps environment (typically Log Analytics).

Why portal/CLI could appear “stuck” while Log Analytics still shows runs?

• Execution history (portal/CLI) = “status of recent executions” (and limited by the most recent 100 successful/failed runs).
• Logs = detailed run output written to the logs provider configured for the environment, which you can query in Log Analytics.

Given your symptom pattern (portal + CLI not updating, but Log Analytics has new system logs), the most likely explanation to check is whether the “execution history” data isn’t being updated/returned as expected even though the job containers are still executing and writing logs.

Try below steps:

1. Confirm you’re querying the right logs tables/providers
   • The docs show example queries against:
     • ContainerAppConsoleLogs_CL (console logs),
   • and mention that job run logs are stored in the logging provider configured for the Container Apps environment (default is Log Analytics).
   • Your query uses ContainerAppSystemLogs_CL that can be useful, but it’s worth also checking ContainerAppConsoleLogs_CL using the job run/container group name pattern shown in the docs.
   Example from docs (adapted):

   
    let job = "<myjob>";
   
    ContainerAppConsoleLogs_CL
   
    | where ContainerJobName_s =~ job
   
    | project TimeGenerated, Log_s, ContainerGroupName_s, EnvironmentName_s
   
    | order by TimeGenerated asc
   
   

2. Use CLI/REST to validate what the service thinks the “execution history” is
   • CLI:

     
      az containerapp job execution list --name "<job-name>" --resource-group "<rg>"
     
     

   • REST:
     • GET .../Microsoft.App/jobs/{job}/executions?api-version=2023-05-01
   If those also stop advancing at the same point as the portal, that points more strongly to an execution-history reporting/metadata issue (as opposed to just a UI/logging query mismatch).
3. Consider the “most recent 100 successful/failed executions” limit
   • If the job has a lot of runs and/or changes behavior, it’s possible that the portal’s limited execution-history set isn’t reflecting what you expect (though your issue sounds like it stopped updating entirely after a date, which is less typical).
4. Diagnose tool error
   • The docs provided don’t include guidance for the “Diagnose tool (Availability and Performance) returns an error has occurred” scenario for Jobs specifically, so there isn’t enough documented info here to pinpoint that part.

Thanks for your reply @Pravallika KV .

ContainerAppConsoleLogs_CL does return logs for the most recent runs in June, and those were successful runs.

However the CLI az containerapp job execution list --name "<job-name>" --resource-group "<rg>" only returns runs in May. The job name and resource group name are identical in both queries.