Container app jobs execution history

Question

Container app jobs execution history

Andrii Zahorodniuk 20

We run several scheduled tasks using Azure Container Apps Jobs once per day. The execution history for these jobs has stopped appearing across multiple subscriptions and different jobs. Log queries indicate that the jobs are still being triggered daily as expected. The last execution history entry visible for all jobs is from 2026-05-31.

Andrii Zahorodniuk 20 Reputation points

2026-06-11T19:50:04.9733333+00:00

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)
Pravallika KV 17,620 Reputation points Microsoft External Staff Moderator

2026-06-15T23:48:23.66+00:00

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

2026-06-18T07:36:56.6866667+00:00

@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
Pravallika KV 17,620 Reputation points Microsoft External Staff Moderator

2026-06-19T01:11:26.1833333+00:00
Hi @Andrii Zahorodniuk / @Tim Bouveng ,

This behavior has been confirmed as a product defect in the Container Apps Job execution-history read path. Engineering has identified the root cause, and the recommended long-term fix is to sort executions by start time before applying pagination, along with proper paging support across Portal and API experiences.

Hotfix to resolve the product bug is in progress ETA 3days.

Until the platform fix is deployed, you can use the following methods to monitor all executions:

1. Use Azure Monitor / Log Analytics Logs

The logs continue to show all executions correctly. You can query:

ContainerAppConsoleLogs_CL

Container Apps system logs

to view the complete execution history.

2. Use CLI or REST API with Pagination

When retrieving job executions through Azure CLI or REST API, ensure all continuation pages are queried rather than relying on only the first page of results. This will return the full execution history.

Hope this helps!
Pravallika KV 17,620 Reputation points Microsoft External Staff Moderator

2026-06-20T01:12:15.23+00:00

Hi @Andrii Zahorodniuk / @Tim Bouveng , following up to see if you had a chance to check the above response and if it was helpful.
Tim Bouveng 0 Reputation points

2026-06-22T06:24:47.5+00:00

@Pravallika KV The executions are now shown correctly again, thanks!
Pravallika KV 17,620 Reputation points Microsoft External Staff Moderator

2026-06-22T15:08:53.8166667+00:00

Thanks for the confirmation @Tim Bouveng , glad its working. If this answers your query, do click Accept Answer =>Yes, and upvote it. If you have any further queries do let us know.

Answer accepted by question author

0 additional answers

Your answer

Andrii Zahorodniuk 20 Reputation points

2026-06-11T19:50:04.9733333+00:00

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)
Pravallika KV 17,620 Reputation points Microsoft External Staff Moderator

2026-06-15T23:48:23.66+00:00

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

2026-06-18T07:36:56.6866667+00:00

@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
Pravallika KV 17,620 Reputation points Microsoft External Staff Moderator

2026-06-19T01:11:26.1833333+00:00

Hi @Andrii Zahorodniuk / @Tim Bouveng ,

This behavior has been confirmed as a product defect in the Container Apps Job execution-history read path. Engineering has identified the root cause, and the recommended long-term fix is to sort executions by start time before applying pagination, along with proper paging support across Portal and API experiences.

Hotfix to resolve the product bug is in progress ETA 3days.

Until the platform fix is deployed, you can use the following methods to monitor all executions:

1. Use Azure Monitor / Log Analytics Logs

The logs continue to show all executions correctly. You can query:

ContainerAppConsoleLogs_CL

Container Apps system logs

to view the complete execution history.

2. Use CLI or REST API with Pagination

When retrieving job executions through Azure CLI or REST API, ensure all continuation pages are queried rather than relying on only the first page of results. This will return the full execution history.

Hope this helps!
Pravallika KV 17,620 Reputation points Microsoft External Staff Moderator

2026-06-20T01:12:15.23+00:00

Hi @Andrii Zahorodniuk / @Tim Bouveng , following up to see if you had a chance to check the above response and if it was helpful.
Tim Bouveng 0 Reputation points

2026-06-22T06:24:47.5+00:00

@Pravallika KV The executions are now shown correctly again, thanks!
Pravallika KV 17,620 Reputation points Microsoft External Staff Moderator

2026-06-22T15:08:53.8166667+00:00

Thanks for the confirmation @Tim Bouveng , glad its working. If this answers your query, do click Accept Answer =>Yes, and upvote it. If you have any further queries do let us know.

Answer 1

Hi @Andrii Zahorodniuk ,

Thanks for the confirmation, glad the issue is resolved.

This behavior has been confirmed as a product defect in the Container Apps Job execution-history read path. Engineering has identified the root cause, and the recommended long-term fix is to sort executions by start time before applying pagination, along with proper paging support across Portal and API experiences.

Hotfix to resolve the product bug is in progress ETA 3days.

Until the platform fix is deployed, you can use the following methods to monitor all executions:

1. Use Azure Monitor / Log Analytics Logs

The logs continue to show all executions correctly. You can query:

ContainerAppConsoleLogs_CL
Container Apps system logs

to view the complete execution history.

2. Use CLI or REST API with Pagination

When retrieving job executions through Azure CLI or REST API, ensure all continuation pages are queried rather than relying on only the first page of results. This will return the full execution history.

Hope this helps!

If the resolution was helpful, kindly take a moment to click on User's image and click on Yes for was this answer helpful. And, if you have any further query do let us know.