---
title: Notifications And Administrator Reruns
description: "AI notification merge tags replace text only. Array values from multi-input fields and other non-text values pass through unchanged, including on GravityView search/edit pages. ## Notification Events Text feeds register these Gravity Forms notification events: - AI text feed completed.…"
url: "https://brightleafdigital.io/docs/notifications-and-admin-reruns/"
updated: "2026-11-18"
category: GravityOps AI Feed / Settings Reference
---

# Notifications And Administrator Reruns

AI notification merge tags replace text only. Array values from multi-input fields and other non-text values pass through unchanged, including on GravityView search/edit pages.

## Notification Events

Text feeds register these Gravity Forms notification events:

- AI text feed completed.
- AI text feed failed.
- All AI text feeds completed.

A normal after-submission text feed emits its individual completion or failure event. The all-feeds event is available for work that should wait until every applicable text feed has finished.

Notification messages can include:

- `` for the configured feed name.
- `` for the provider or processing error associated with a failure event.

## What An Administrator Rerun Is

On Premium and Agency, an administrator with Gravity Forms full access can open a saved entry and use the **AI Feed Rerun** box to run one of that form's AI feeds again.

A rerun:

- Uses the current saved entry values and current feed settings.
- Makes a new provider request and can create additional provider cost.
- Force-overwrites the configured text destination values, even when Existing Values is set to Fill only empty targets.
- Generates and saves a new image result for an image feed.
- Is protected against two simultaneous reruns of the same feed and entry.
- Does not require the feed's normal Trigger Mode to be After Submission.

After a successful rerun, the entry page reloads so the newly saved text or image, entry notes, and related metadata are shown immediately.

Use reruns after correcting entry data, adjusting a prompt, recovering from a temporary provider failure, or deliberately requesting a new result. Review downstream automations before replacing values used by other systems.

## Rerunning A Feed That Uses Tools

A feed with MCP tools acts on other systems, and a rerun acts on them again. The rerun button asks for confirmation first. See [MCP Servers And Tools](https://brightleafdigital.io/docs/mcp-servers-and-tools/).

## Rerun Notifications

The **Rerun Notifications** checkbox means: after an administrator manually selects the rerun button, also emit this text feed's completion or failure notification event.

Leave it off when manual retries should quietly update the entry. Enable it when notification recipients or integrations must be told about the replacement result. It does not enable the rerun feature itself and it does not affect normal post-submission notifications.

## Workflow Notifications

The **Workflow Notifications** checkbox emits this text feed's completion or failure event after the feed runs as a Gravity Flow step. Leave it off if the workflow itself handles communication.

## Stuck? Ask in GravityOps Help

Search past answers or post your question, tagged "ai-feed".

- [GravityOps AI Feed: a feed did not run on submission](https://brightleafdigital.io/community/gravityops-help/4147/)GravityOps Help - 0 replies - 2 weeks ago
- [GravityOps AI Feed is live: Claude and OpenAI as Gravity Forms feeds](https://brightleafdigital.io/community/announcements/3931/)Announcements - 0 replies - 4 weeks ago

[Ask in GravityOps Help](https://brightleafdigital.io/community/gravityops-help/?gofrm_tag=ai-feed)[Open a support request](https://brightleafdigital.io/support/)

GravityOps Weekly

[This iframe contains the logic required to handle Ajax powered Gravity Forms.](about:blank)
