Workflow Retry Design with Codex: API Runtime Pattern
A production playbook for workflow retry design in cross-industry operations using Codex: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Backend engineers building reliable agents
The problem
Backend engineers building reliable agents need workflow retry design to run repeatedly against terminal states, retry policies, idempotency keys, and failure logs. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the workflow retry design instructions as a skill, send terminal states, retry policies, idempotency keys, and failure logs as run-scoped inputs, execute with Codex, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For workflow retry design, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=codex
workflow=workflow-retry-design
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo