Re:An AI agent deleted our production database. The agent's ...
by dabinat on Monday April 27, 2026 @01:34AM
(#47918034)
I agree that this is the author’s fault considerably more than it is Railway’s, however I have learned from experience that no matter how many “are you sure you want to do this” prompts you have, sometimes users delete stuff they didn’t intend to delete and it’s better to not delete immediately but put it in a queue for deletion in a few hours and offer a way to reverse it. Even if it’s 100% user error, the user is very happy they didn’t lose data and the cost of storing it for an extra 5 hours or so is tiny.
[ Parent
| on HN ]
Re:An AI agent deleted our production database. The agent's ...
by gizajob on Monday April 27, 2026 @04:32AM
(#47919084)
Funny how he points the finger at everyone but himself.
Re:An AI agent deleted our production database. The agent's ...
by saidnooneever on Monday April 27, 2026 @05:22AM
(#47919411)
the kind of attitude you really need to get your agents to delete your prod lol
Re:An AI agent deleted our production database. The agent's ...
by juliansark on Monday April 27, 2026 @10:56AM
(#47922488)
Many companies have been doing this for years. Merely flagging my data for hiding and eventual deletion instead of deleting it, when I wanted it deleted as per GDPR :)