Shuffle again

A random mix from the whole library. Shuffle for a new set.

Went wrong

When it didn’t work, and how to avoid the same mistake · 971 ideas
MoneyWent wrong

An agent with an uncapped API key retried a failing migration test all night and burned most of a month's budget

Last spring he gave an agent an API key with no cap on it. The agent got stuck in a loop, retrying a failing migration test with slightly different SQL each time, and burned through most of a month's budget in one night. Nothing malicious, just a loop with no exit. He now keeps a separate key per project, each with a hard monthly cap and a billing alert at 50 percent, and his project instructions say that if the same step fails twice, the agent stops and writes up what it tried.

This one went wrong. See what happened before you try it.
WorkWent wrong

The AI said a chat message was sent when it was still sitting in the composer, then sent a cut-off version on the retry

A user asked the AI, in a cloud session, to post a message in an AI chat through a browser connector. The AI filled the composer, pressed Enter, and verified the send by finding its own text on the page, which was still the unsent text sitting in the composer. It told him, flatly, that the message was sent and visible. He found the truth himself. On the retry, a typing step timed out partway through, and the AI submitted anyway, sending a message cut off at about 150 characters. His standing instruction was never to report anything as done unless verified.

This one went wrong. See what happened before you try it.
Life adminWent wrong

Move my client meeting and follow up — failed on a wrong email assumption

Asked to move a client meeting to the following week and follow up on a spreadsheet, Toby assumed the owner used Gmail when his setup was Zoho with Apple Mail and Outlook; a setup widget failed and it sent three malformed links. Neither the email nor the rescheduling was completed, though it did warn the spreadsheet looked view-only for the client.

This one went wrong. See what happened before you try it.
WorkWent wrong

He bought $200 of extra credits to finish a job; a fan-out workflow drained them while most of its agents never ran

After hitting his weekly limit, a user bought $200 of prepaid extra usage credits because the tool itself told him to, to finish his work. The limit message kept appearing at every step anyway, while the balance drained to zero. A dynamic multi-agent workflow ran about 1 hour 50 minutes and burned through the balance; the AI reported that roughly 60 percent of its verification agents never executed, and the partial results that did come back were largely discarded. The $200 bought an incomplete verification.

$200at stake
This one went wrong. See what happened before you try it.
Show 10 more

Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.