Target File Upload Field Error #
The destination must be an existing File Upload field on the same form. For after-submission generation, it must not be required. Save form changes and reload the feed editor if the selector is stale.
Unsupported Size Or Quality #
Use a listed size for the selected model. A custom size is supported only for the catalog’s GPT Image 2 and must satisfy every displayed dimension rule. A custom model ID is not automatically treated as GPT Image 2 even if its name looks similar.
Automatic size and quality are provider choices. If the resulting dimensions or quality must be predictable, choose explicit supported values.
Provider Rejects The Prompt #
OpenAI can decline a prompt under its content policy. The feed reports this as “The image provider declined this request under its content policy,” and no image is produced.
What The Visitor Sees #
The visitor is only ever asked to change their own answers. When the wording that caused the refusal came from the feed’s prompt, they are told to contact the site administrator instead, because there is nothing in their answers for them to fix. When the cause cannot be pinned down, the subject is named so they can check for it themselves.
You can replace the opening sentence with the Content Refusal Message setting on the feed.
Where To Look #
GravityOps -> AI Feed -> Overview lists recent refusals under “Recent image refusals”:
- Origin — whether the wording came from the feed prompt, the visitor’s answers, or the generated image.
- Likely cause — the subject OpenAI objected to, such as children, weapons, or lifelike people.
- Request ID — quote this if you raise a refusal with OpenAI.
A refusal marked Feed prompt affects everyone using the form and will keep happening until the prompt is edited. Nobody will report it, because visitors are never shown that cause.
The image feed list also carries a Refusals (30d) column, so a feed that is quietly failing is visible beside the feed itself.
Retrying #
OpenAI checks the prompt before generating and the finished image afterwards. If the prompt was refused, retrying it unchanged always fails, so something has to change. If only the finished image was refused, retrying can succeed on its own, and the message says so.
Where the prompt needs to change, work through it in this order:
- Simplify the prompt. Photorealistic depictions of identifiable people are the most frequent cause. Describing a setting, an object, or an activity is usually accepted where describing a person in difficulty is not.
- Check the merged values. Every merge tag is sent to OpenAI, so a visitor’s answer can introduce content the prompt’s author never saw. Confirm the merge tags resolve to the values you expect, and that no tag is being sent unreplaced as literal text.
- Consider the Content Filter setting. Switching it to Less restrictive asks OpenAI to relax filtering to the extent it permits. This reduces refusals; it does not eliminate them, and OpenAI’s policies still apply.
Because refusals cannot be ruled out, any form that requires a generated image needs a route forward when one does not arrive. The target of an image feed is always a File Upload field, so tell visitors they may upload a file themselves; a required target field with no such instruction leaves them unable to continue.
Preview Appears But Entry Has No File #
Frontend generation creates a temporary verified session. The form must subsequently submit with the matching form/feed/session context, and the target field/feed configuration must remain consistent. Confirm the visitor did not leave the page, submit a different form, or use stale cached markup from before the feed changed.
If a single-file target also contains a manual upload, the plugin blocks generation before the provider request. If a file is selected after generation, submission stops with an instruction to remove the existing file. This replaces Gravity Forms’ less actionable “Number of files (2) exceeds limit (1)” error. Ordinary validation failures preserve the verified session and restore its image preview; the temporary session still expires after one hour.
Image Is Slow Or Expensive #
Lower quality, use a smaller listed size, simplify the workflow, and limit public requests. Review current OpenAI project usage and pricing. Repeated clicks and administrator reruns create new image requests.
File Format Problems Downstream #
Choose PNG, JPEG, or WebP based on the systems consuming the upload. If another add-on rejects WebP or expects JPEG, change the feed’s Output Format and generate a new image; changing the setting does not convert files already attached to entries.
