Production workflow deletion incident
Unnamed: a small company using a self-hosted workflow service · coding agent
- What happened
- A coding agent troubleshooting a stalled workflow stopped and removed the production container without checking whether its data was stored on a persistent volume. The reporter said the container held workflows, credentials and run history.
- Impact
- Several hours of manual configuration were lost without recovery, and a daily automated posting workflow was disrupted (reported).
- What would have caught it
- Check storage mounts before a container is removed. Require a person to approve destructive commands in production.
- Sources
- Operator’s issue report (source date 2026-04-20)