Target Field Is Missing From The Selector #
Save the form after adding the field, then reload the feed editor. Confirm you are editing a feed belonging to that form. Image target selectors intentionally show only File Upload fields.
Text destinations are configuration-aware. Common reasons a field is absent include a calculated Number, an unsupported Phone format, a choice field without resolvable current choices, a stale multi-column List definition, or an unavailable add-on field class. US Standard and International (unformatted) Phone formats are supported; International (formatted) additionally requires country/dial-code data from the installed Gravity Forms version. See the output-fields reference for the complete configuration table.
If the field is present but disabled, either it requires a higher subscription plan or another Output Map row already selected it. Change or remove the other row to release the field.
Single Target Field Initially Hidden #
New feeds default to Single target field and should show the selector on first load. If an older browser tab was opened before the form or plugin changed, reload the page rather than toggling Output Mode to repair stale page state.
Invalid Or Missing JSON Property #
Confirm every mapping row has a unique Response name and a selected destination. Names are exact and case-sensitive. Put each property’s requirements in that row’s Output instructions; keep the common source material and shared behavior in the prompts.
For custom or older models without native structured-output support, the provider follows a prompt instruction to return JSON. Such a model can still add prose, omit a property, or return invalid JSON. Prefer a listed current model with structured-output support when reliability is important.
If the provider reaches the feed’s Max Tokens limit, its JSON may end mid-property. The plugin does not guess at values inside malformed or truncated JSON. Raise Max Tokens and retry; the matching Ledger event records max_tokens when Anthropic explicitly reports that stop reason.
A Destination Was Not Written #
For saved entries, review the outcome and entry note. For frontend buttons, review GravityOps -> AI Feed -> Ledger. A partial run means valid destinations were retained while one or more missing, invalid, or failed destinations were skipped. The note or ledger diagnostic identifies fields and safe reason messages without including generated values.
Confirm the field still exists and retains the configuration used when the feed was saved. Choice values, List columns, calculation settings, effective choice modes, and add-on field availability can all make a saved destination stale. Reopen and resave the mapping after changing the form.
The Generated Value Does Not Match The Field #
Typed destinations validate semantic values rather than coercing every response to text. For example, Number requires a number; Select and Radio require one current choice value; Checkbox and Multiselect require arrays of current choices; Date requires a calendar date; and compound fields use structured objects. Adjust the row’s Output instructions and use the live field choices rather than asking for labels or formats the destination does not store.
A Populated Field Was Left Alone #
With Fill only empty targets, populated destinations are excluded from the provider request. If every destination is populated, the feed skips generation. Choose Overwrite configured targets for normal executions that should replace them, or use an administrator rerun for a deliberate one-time force overwrite.
Generated Values Are Altered #
Generated output is sanitized before saving. HTML or control content can be removed or normalized according to the destination. Choose a suitable destination and request plain text when exact markup is not required.
Tags Such As <p> Appear As Text In The Rich Text Editor #
A rich-text destination accepts both HTML and Markdown, and the format is detected from the output itself. Tags showing as literal text mean the output was not recognized as HTML — usually because the only markup in it is a tag the sanitizer does not allow, so nothing recognizable survives the safety pass. Have the prompt use paragraph, strong, emphasis, heading, list, or link tags, or drop the tags and let it return Markdown. goaif_generated_value_is_html can force the decision either way; see the developer reference.
Plain Paragraph Text fields never keep tags: the sanitizer flattens the markup into text, keeping the paragraph breaks. Enable Use the Rich Text Editor on the destination if the generated markup itself has to survive.
Entries saved before 1.0.6 can still hold escaped tags, because fixing the sanitizer does nothing for values already in the database. A one-time background repair runs after upgrading and restores those values; it works through them in batches on WP-Cron and touches nothing else.
