← All insightsBest Practices

Common Argo Workflows mistakes and how to avoid them

CodeWizard Academy · 29 October 2025 · 3 min read · Intermediate

Most Argo Workflows pain is self-inflicted and predictable. Here are the mistakes we see most, and the fix for each.

Mistake 1: No resource limits on step containers

Fix: Set limits and activeDeadlineSeconds on templates. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.

Mistake 2: Unbounded retries hammering the cluster

Fix: Use workflow GC (TTL) to clean up finished runs. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.

Mistake 3: Keeping completed workflows forever, bloating etcd

Fix: Store artifacts in object storage, not the cluster. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.

A safer baseline

A DAG workflow with dependencies.

yaml
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata: { generateName: build- }
spec:
  entrypoint: main
  templates:
    - name: main
      dag:
        tasks:
          - { name: build, template: run, arguments: { parameters: [{ name: cmd, value: make build }] } }
          - { name: test,  template: run, dependencies: [build], arguments: { parameters: [{ name: cmd, value: make test }] } }
    - name: run
      inputs: { parameters: [{ name: cmd }] }
      container: { image: alpine, command: [sh, -c], args: ['{{inputs.parameters.cmd}}'] }

Want senior help putting Argo Workflows to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult