Argo Workflows Archive Quick Fix - Workflow History Storage
DodaTech
Updated 2026-06-26
1 min read
Argo Workflows archive stores completed workflow runs in a database for historical access. Misconfigured archive settings cause data loss or database connection failures. This guide covers the fix.
Quick Fix
Wrong
persistence:
archive: true
postgresql:
host: postgres
database: argo
The issue: missing connectionPool settings, no tableName specification, and no password reference. The archive connection fails with authentication errors.
Right
persistence:
archive: true
postgresql:
host: postgres.argo.svc
database: argo
tableName: argo_workflows
passwordSecret:
name: argo-postgres-config
key: password
connectionPool:
maxIdleConns: 100
maxOpenConns: 200
# Expected output after applying the fix
# Workflow archive connected to PostgreSQL
# Completed workflows stored in argo_workflows table
# Historical runs accessible via `argo list --all`
# Archive retention: default (permanent)
Prevention
- Configure
passwordSecretfor database authentication - Set
connectionPoolparameters for production workloads - Specify
tableNameto avoid name conflicts - Configure retention policies to manage storage costs
- Verify archive with
argo list -n <ns> --chunk-size 10
DodaTech Tools
Doda Browser's archive explorer searches and retrieves historical workflow runs. DodaZIP archives database configurations for disaster recovery. Durga Antivirus Pro secures archive database connections.
FAQ
← Previous
Argo Workflow Failure Fix
Next →
Argo Workflows Artifact Quick Fix - Artifact Passing Errors
Built by the developers of DodaTech
Doda Browser, DodaZIP & Durga Antivirus Pro