Work through these checks in order.
1. Native Feed Status #
Open GravityOps -> AI Feed -> Feeds or the form’s feed list. Confirm the feed is Active. The plugin uses Gravity Forms’ native activation state and has no second Feed Enabled checkbox.
2. Trigger Matches The Action #
- A submission runs only After form submission.
[goaif_button]requires the complete-result or either-button text trigger.[goaif_stream_button]requires the streamed-result or either-button text trigger.[goaif_image_button]requires the image Frontend button trigger.- Administrator reruns and Gravity Flow steps are explicit paths and do not require the normal trigger to match.
3. Global Controls #
Check whether the provider is disabled, the entire form is selected under disabled forms, or a monthly text cap has been reached. A reached form cap can block a feed even when its feed cap is blank.
4. Conditional Logic #
Confirm the entry values meet the feed condition. For frontend buttons, complete fields before selecting Generate. Values on a later unvisited form page may not exist yet.
5. Provider And Model #
Test credentials. Confirm the selected model is available to the provider account. For a custom model, verify the exact API ID and endpoint compatibility.
6. Entry Notes And Debug Log #
Open the Gravity Forms entry and review notes for skipped budgets or generation errors. With WordPress debugging enabled, review wp-content/debug.log for relevant plugin/provider failures, but do not copy secrets into diagnostic output.
Async text feeds run after submission, so wait for background processing before treating an empty field as a failure.
