Container Apps Jobs¶

Azure Container Apps Jobs run bounded background work with a defined start and finish. Use this section to choose a trigger model, understand execution fan-out, and operate jobs safely in production.

Main Content¶

What this section covers¶

• Manual Jobs for operator-driven backfills, maintenance, and replay.
• Scheduled Jobs for cron-based recurring execution.
• Event-Driven Jobs for queue- or event-triggered one-shot processing.
• Execution Lifecycle for execution states, retries, timeouts, and retention.
• Jobs vs Apps for workload selection.

When to choose Jobs¶

Choose Jobs when:

• Work is finite and success is defined by completion.
• Retries can safely re-run the same unit of work.
• Triggering should happen manually, on a schedule, or from an event source.

Choose Container Apps instead when:

• You expose ingress and continuously handle requests.
• A process should stay warm and consume work continuously.
• You want scale decisions to adjust long-running replicas instead of starting discrete executions.

Reading path¶

1. Start with the trigger guide that matches your workload.
2. Read Execution Lifecycle before tuning parallelism or retries.
3. Use Jobs vs Apps if the workload boundary is still unclear.
4. Apply Job Design before production rollout.
5. Use Jobs Operations for replay, inspection, and monitoring.

Jobs document map¶

flowchart TD
    A[Container Apps Jobs] --> B[Manual Jobs]
    A --> C[Scheduled Jobs]
    A --> D[Event-Driven Jobs]
    A --> E[Execution Lifecycle]
    A --> F[Jobs vs Apps]
    E --> G[Job Design]
    E --> H[Jobs Operations]
    H --> I[Troubleshooting]
    F --> J[Language Recipes]

See Also¶

• Platform Overview
• Job Design
• Jobs Best Practices
• Jobs Operations
• Python Jobs Recipe

Sources¶

• Jobs in Azure Container Apps (Microsoft Learn)
• Scale jobs in Azure Container Apps (Microsoft Learn)