Idle projects can still bill: check background tasks and storage
@An_yhl reads @shmily7’s follow-up as a reason to audit abandoned AI projects: check scheduled background work and storage reads and writes, stop what is unused instead of just closing the page, and turn on alerts knowing they will not stop anything.
- Products
- Durable ObjectsWorkers
- Source
- Author experience𝕏
- Author
- @An_yhl
Key points
- Citing @shmily7’s follow-up, the author notes that the test project had no users and its alarm woke into a loop 23 days after being shelved, so a project with no visitors can still burn money.
- Her first step is to check background scheduled tasks and storage reads and writes, and stop unused projects rather than only closing the web page.
- She also says to turn on billing alerts, while noting that alerts will not shut services down for you.
Original sources
Original source · Published
Read on 𝕏晚晚
@An_yhl · Original 𝕏 post
Cloudflare 那张一万多美元账单有后续了 当事人说已处理退还 $10,701.41 还在等到账 我看完最想干的事 是翻一下自己那些试完就扔着的 AI 项目 他这个测试项目没人用 搁置后 23 天 alarm 才醒过来死循环 没人访问 照样能烧钱啊 先查后台定时任务和存储读写 不用的停掉 别只把网页关了…
More to read
A budget alert is a horn, not a brake
@GUYUE_LGY points to Cloudflare’s Budget alerts documentation: alerts send email when spend crosses a threshold but do not pause or cap usage. Before letting AI run unattended, the author checks what actually happens at the line.
mcwangcn reports $1,300 in D1 charges after a bot attack.
@mcwangcn says D1 writes previously cost over a thousand dollars and separately mentions Workers CPU charges without giving an amount. He later shares a Cloudflare bill and says $1,300 of its $3,600 came from D1 after a bot attack.
cloudflare-cost-guard
Louis Cai’s open-source rules and TypeScript base class for keeping Durable Object alarms and Worker schedulers from runaway loops.