Feed Settings

This reference covers all fields in the Recurring Submissions feed editor at the form level. It documents labels exactly as shown in the UI, notes defaults, and explains runtime behavior.

Path Forms → [Form] → Settings → Recurring Submissions

---

Feed Settings (Header Section) #

Feed Name #

Type: Text Required: Yes Purpose: Administrative name for the feed. Appears in admin lists and logs.

Feed Label #

Type: Text with merge tag support Required: No Default: Feed Name + Entry ID (auto‑generated) Purpose: Human‑readable label for the specific series created from an entry. Use merge tags to personalize by entry data (e.g., Invoice for {Name (First):2.3} → Invoice for John).

Guidance: Hard‑coding a static label makes it identical for every entry. Use merge tags (entry meta/field tokens) to make labels entry‑specific and easier to identify at scale.

Conditional Logic #

Type: Standard Gravity Forms conditional logic control Required: No Purpose: Gate whether the series should start for a given entry. Logic is evaluated at the time of the parent submission. If conditions are not met on the parent, the series does not start.

---

Critical Concept: Settings Snapshots #

When a series starts (triggered by a parent entry), the plugin takes a snapshot of all feed settings (cadence, limits, etc.).

• Edits to this feed will not retroactively update active series that have already started.
• Only new series created after you save the feed will use the updated settings.

Time Interval (Required) #

Label: The form should re‑submit every Type: Number + Unit selector Units: Day(s), Week(s), Month(s), Year(s) Purpose: Defines the cadence between the parent submission and each resubmission.

---

How do you want to limit your resubmissions? (Required) #

Choose one of the following controls to define when the series stops.

Option A — Number of resubmissions #

Follow‑up Field: Number of resubmissions (Required) Type: Integer Meaning: How many additional submissions to create beyond the parent. Notes: This is only resubmissions; the parent is not counted.

Option B — Stop at a specific date #

Follow‑up Field: End Date (Required) Type: Date Meaning: The series will not schedule resubmissions after this date.

Option C — Number Field on Form #

Follow‑up Field: Select a Number Field (Required) Type: Dropdown of number fields on the current form Meaning: The selected field’s value on the parent entry controls total resubmission count. Again, this is amount of resubmissions, excluding the parent submission.

---

Snapshot Entry Inputs Now #

Type: Checkbox Default: Unchecked Purpose: Controls value sourcing for resubmissions.

• Unchecked (default): Rebuild from current entry state
  • Before each resubmission, the plugin reloads the entry and uses its current values.
  • GPPA (Populate Anything) sources re‑hydrate at run time.
• Checked: Snapshot now
  • The plugin stores the entry’s values at the moment the parent is submitted and reuses that snapshot for all resubmissions.
  • GPPA values are copied from the parent (i.e., they remain the same on children).

Conditional Logic (Potential Child Entry) #

Type: Checkbox Default: Checked Purpose: When enabled, the feed’s conditional logic is evaluated against the values that are about to be submitted (including any updates to date fields).

• Checked: If logic fails, the specific resubmission is skipped, but the series remains active for future dates.
• Unchecked: Logic is not checked against the child entry data.

Conditional Logic (Current Parent Entry) #

Type: Checkbox Default: Unchecked Purpose: When enabled, the feed’s conditional logic is evaluated against the current values of the parent entry in the database.

• Checked: If logic fails, the specific resubmission is skipped. Useful for checking “Status” fields on the parent entry (e.g., stop if status is “Cancelled”).
• Unchecked: Logic is not checked against the parent entry database values.

Note: If both checkboxes are enabled, both conditions must be met for the resubmission to proceed.

General Notes:

• Calculation fields: Gravity Forms recalculates calculation fields on each submission.
• Unique ID fields: Always generate new values per resubmission regardless of Snapshot or Rebuild mode.
• Number Field on Form: When used to control resubmission limits, its value will always be 0 on resubmissions to differentiate child entries from their parent, regardless of mode.

---

Update Date Field(s) #

Type: Multi‑select of Date fields on the form Required: No Purpose: When selected, these fields are populated with the date at time of resubmission (instead of copying the parent’s date). Useful for invoice dates, service periods, etc.

---

Runtime & Validation Notes #

• Every resubmission is a new Gravity Forms entry and must pass normal form validation. If validation fails, no feeds run and the attempt is logged as a failure.
• All times are displayed in the site time zone.
• Parent/child relationships are recorded via entry notes and metadata for traceability.

---

Field Summary (Quick Table) #

Section	Field	Required	Default	Notes
Feed Settings	Feed Name	✓	—	Admin label
Feed Settings	Feed Label		Feed Name + Entry ID	Merge tags supported
Feed Settings	Conditional Logic		Off	Standard GF logic
Submission Settings	Time Interval	✓	—	Number + Unit (Days/Weeks/Months/Years)
Submission Settings	Limit: Number of resubmissions	✓ (if selected)	—	Follow‑up: integer count
Submission Settings	Limit: Stop at a specific date	✓ (if selected)	—	Follow‑up: date + time
Submission Settings	Limit: Number Field on Form	✓ (if selected)	—	Follow‑up: select number field
Submission Settings	Snapshot Entry Inputs Now		Unchecked	Determines Snapshot vs Rebuild behavior
Submission Settings	Conditional Logic (Child)		Checked	Evaluates logic against potential submission data
Submission Settings	Conditional Logic (Parent)		Unchecked	Evaluates logic against current parent entry in DB
Submission Settings	Update Date Field(s)		None	Sets date at resubmission