Button Does Nothing Or Reports Wrong Trigger #
Verify the shortcode feed ID and Trigger Mode. Confirm the shortcode rendered inside the intended form so the button can collect values and find target fields. Check browser developer tools for a blocked AJAX request or JavaScript error.
Could Not Start Generation #
The button first requests a single-use token. Confirm the Premium/Agency entitlement is active, the feed and form exist, the feed is Active, and the public token endpoint is not blocked by a security plugin, firewall, or cache rule.
The Visitor Sees A General Generation Error #
Provider, schema, configuration, and field-write details are deliberately not shown to public form visitors. An administrator can open GravityOps -> AI Feed -> Ledger and find the newest event for the form and feed. The ledger shows its outcome, token counts, error code, safe diagnostic, and provider request ID without storing the prompt or generated values.
The public message remains specific when the visitor has a useful next step, such as waiting for a rate limit, changing form values required by conditional logic, or revising their own wording after an image content-policy refusal.
An output-token count equal to the feed’s Max Tokens value together with a max_tokens diagnostic means Anthropic stopped before completing the response. Increase Max Tokens enough for the entire answer. This is especially important for JSON mappings because truncated JSON cannot be parsed or partially trusted.
Administrator Permission Required #
The feed is configured for Gravity Forms administrators only. Log in with an account that has gform_full_access, or deliberately change the feed to signed public access after reviewing public rate limits and costs.
Rate Limit Exceeded #
Wait for the configured window to reset. If many legitimate visitors share a CDN or load balancer network identity, review trusted-proxy configuration with the hosting/network administrator. Do not increase limits before ruling out abuse or a repeated-click design problem.
Streaming Appears All At Once #
The provider and plugin may be streaming correctly while a reverse proxy, web server, optimization plugin, or hosting layer buffers the response. Test with caching/minification disabled on a staging page and ask the host whether Server-Sent Events are buffered. The response sends X-Accel-Buffering: no, prevents cache transformations, and drains removable PHP output buffers, but an upstream layer may ignore those controls.
Older browsers without a readable streaming response body fall back to processing the completed stream, so they can display the result only at the end.
JSON-mapped feeds and typed single targets deliberately do not preview streamed text because that text is the provider’s structured contract. The button remains in its working state until the completed value can be validated and applied to the destination fields. Plain Text, Paragraph, and Hidden single-target feeds can continue to preview text incrementally.
Result Does Not Fill A Field #
Keep the button inside the form and verify that the destination field is rendered on the page. Frontend adapters can fill the supported text, numeric, date/time, choice, Name, Address, List, Entry Tags, and rich-text destinations documented in the output reference. A field on an unrendered conditional or multipage section cannot be updated visibly. A third-party server-only adapter also needs the frontend adapter contract before a frontend trigger can use it.
For a valid JSON object, the plugin applies each valid mapped destination independently. If one property is missing or one generated value is rejected by its current field configuration, the other valid fields remain populated and the visitor receives a general partial-result message. The Ledger identifies the skipped destination and reason. If the response itself is malformed or truncated JSON, no trustworthy properties exist to apply and the whole frontend request fails.
GravityKit Entry Tags destinations update both the original field value and the visible Tagify tags. If the entry receives tags but the form still does not show them, check for a JavaScript error or a theme/optimization conflict that prevented the installed Entry Tags widget from refreshing.
