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 · 946 ideas
WorkWent wrong

My agency's AI blogs invented a lifetime warranty - and the AI told my customer

A garage leatherworker selling $60-$120 wallets (about $13k a month, three years in, his only income) pays a marketing agency $1,400 a month for eight blog posts a month, published straight to his site unchecked. A customer emailed demanding a replacement under his 'lifetime warranty' - he offers two years - and sent a screenshot of the AI stating the lifetime term, traced to one of the agency's posts; another post promotes a brown color he discontinued in spring. Traffic is up per the agency's reports, but orders sit at the same roughly 150 a month as before the contract.

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

Build my game prototype and get it onto my phone — third route worked

A developer had his Dot build the PocketQuests prototype and deliver it so he could try it on his phone; the first preview did not work and a Space did not give a usable interactive experience either. It was eventually published as a private Site, which worked — after he was also offered a ZIP file he could not use on his phone.

This only partly worked. Worth knowing before you try it.
HobbiesWent wrong

Browse for me by voice — cloud computer died after a reset

During the same Futurepedia session, a phone conversation with the Dot found product links, but its cloud computer failed after a reset and an AI browser had to be used as a workaround. The scheduled-task tab also would not open during the recording.

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

My AI burned 43% of my credits fixing videos overnight

Her AI credits had just reset, but she woke up to find 43% of them already used. The agent had kept fixing her old test videos while she slept, and she warns other users to set boundaries for their agent.

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

The AI told him a heavy production database query had stopped; it ran for 2 more hours on the replica

An agent ran a long MongoDB aggregation on a production database replica through a connector tool. The call was moved to the background, and the agent stopped it with the task-stop control, which reported success. The agent told the user the query had been stopped. Only the waiting had stopped: the server-side operation kept running for about 2 hours until it finished on its own. Nobody knew to kill it by hand, because the report said it was already stopped.

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

My daily job digest sent me the same five jobs for two weeks

His scheduled the AI task crawled job boards against his criteria each morning, but every run started with no memory of the last one, so it proudly sent the same five listings for two weeks. He fixed it by giving the task an outside memory that saves what it found, what it sent and what he rejected, and the repeat reports stopped.

This only partly worked. Worth knowing 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.