Getting error "image The image was not created because the image-generation action stopped early after a temporary prompt-budget limit was reached"

I’m running into a persistent error when a Pickaxe tries to use the Generate GPT Images action, and I’ve ruled out everything on my end that I can check, so I’m hoping you can help pinpoint what’s happening server-side.

The error (verbatim, from the agent’s own response):

The image was not created. The image-generation action stopped early because a temporary prompt-token budget limit was reached, so there is no finished asset or image link.

This happens consistently, across multiple retries, with both shorter and longer image prompts.

What I’ve already checked and ruled out on the OpenAI side:

  • Organization verification: confirmed Verified
  • API credit balance: positive ($6+ available)
  • Organization spend limit: well under cap (~$17 of $120)
  • Project-level model allow/block list: no restriction active
  • Tried both: (a) the action set to use Pickaxe’s shared credit pool, and (b) a dedicated OpenAI API key wired directly into the action’s OPENAI_API_KEY variable — identical error both times

Since switching to a dedicated key didn’t change anything, this doesn’t look like an OpenAI-account-side issue — it points to something on Pickaxe’s own infrastructure (the phrasing “prompt-token budget limit” doesn’t match any OpenAI error format I’m aware of).

Setup details:

  • Workspace: KAVIX Studio /// NEXUS-powered coaching workspace
  • Pickaxe: KAVIX Visual Studio (id: kavix-visual-studio)
  • Action: Generate GPT Images (id: ACTION0RWD1GPWOS4J9TI702OD)
  • Model: GPT-5.6 Terra

Hi @chrisbehnke ,

Thank you for reaching out!

The “temporary prompt-token budget” refers to an internal spending limit Pickaxe creates for the agent that coordinates actions. A bug caused your workspace access group to be read incorrectly, so that internal agent received a much smaller allowance than intended. This is also why switching the image action to your own OpenAI key did not help.

We have corrected the access-group calculation and deployed the fix. There is no Builder setting you need to change.

We also found that, in at least one attempt, the image action completed but the surrounding agent failed before returning the image link. The deployed budget fix should prevent the failure you encountered, but we are also investigating how completed assets are preserved if a later workflow step fails.

Please retry the action, preferably in a new conversation. If it still fails, send us the approximate timestamp and session ID so we can trace the new attempt.

Thank you again for reporting this.