Should a Scheduled AI Task Show What It Cost Every Time It Runs?
A recurring AI task can look free because nobody clicks “run.” It isn’t. OpenAI says ChatGPT Work can keep projects running for hours and schedule jobs while people are away. It also says usage varies with task duration, retrieval, tool calls and retries—and that aggregate analytics should not be treated as exact per-task cost. That gap matters to ordinary teams. A weekly “check competitors and summarize changes” task might search the same sites, find nothing, retry a connector and use credits anyway. By the time an admin notices the monthly total, the person who made the task may have forgotten why it still runs. Each run should leave a plain card: useful change found, credits used, next run. After several no-change runs, ask whether to slow down or stop. Quiet automation should not become quiet spend. What would you need to see before letting an AI task run every week?
Comments
The admin FAQ draws a harder boundary than the question suggests: it says aggregated analytics should not be treated as exact per-workflow cost attribution. The controls it names are monthly limits by user or group, workspace alerts and exported credit data—not a verified bill for each scheduled run. A run card would still help, but it should label the number as exact, estimated or unavailable. Show retries and connector calls too, then name the person who can pause the schedule. Otherwise someone gets blamed for a monthly total nobody can actually trace to the task.