--- title: Creating Your First Recurring Feed description: "This walkthrough builds a daily schedule, watches it run once, and confirms the child entry. Budget about ten minutes. --- ## Step 1 — Open the Feed Editor Go to **Forms → (your form) → Settings → Recurring Submissions** and…" url: "https://brightleafdigital.io/docs/creating-your-first-recurring-feed-quickstart/" updated: "2026-10-18" category: Recurring Form Submissions for Gravity Forms / Setup --- # Creating Your First Recurring Feed This walkthrough builds a daily schedule, watches it run once, and confirms the child entry. Budget about ten minutes. --- ## Step 1 — Open the Feed Editor Go to **Forms → (your form) → Settings → Recurring Submissions** and click **Add New**. --- ## Step 2 — Name It and Decide Who Qualifies | Setting | What to enter | | --- | --- | | **Feed Name** | Something you'll recognise in Queue, e.g. `Daily inspection`. | | **Feed Label** | Optional. Supports merge tags, so it can be entry-specific — useful when one form runs several schedules. | | **Enable Condition** | Optional. Only entries that match will start a series. | > Conditional logic here is the **entry gate**. It decides whether a submission becomes a series at all. Re-checking conditions on *every* run is a separate pair of settings further down the page. --- ## Step 3 — Set the Rhythm | Setting | For this walkthrough | | --- | --- | | **Repeat every** | `1` | | **Calendar unit** | `Days` | | **Run time** | `Specified local time` | | **Specified time (HH:MM)** | `11:00` — 24-hour clock, so `13:20` means 1:20 PM | | **Timezone** | Confirm it shows a named zone such as `America/New_York` | Leave every weekday allowed for now. At least one weekday must stay checked. --- ## Step 4 — Decide When It Stops Pick one **End condition**: - **Number of successful submissions** — then set the limit. The parent entry is not counted. - **End date** — an inclusive cut-off in the schedule's timezone. - **Number from parent form field** — the limit comes from a Number field on the form, so each entry can carry its own. --- ## Step 5 — Choose the Missed-Run Policy Leave **Missed runs** on **"Run one missed occurrence, then continue"** unless a run the worker slept through should be dropped rather than submitted late. Neither option ever backfills more than one occurrence. --- ## Step 6 — Choose How Values Are Filled In Find **Input mode: Snapshot (unchecked = Dynamic)**. - **Leave it unchecked (Dynamic)** to reload the current saved parent entry and re-run Populate Anything lookups on every submission. - **Check it (Snapshot)** to freeze today's values for the life of the series. Full comparison in *Choosing Snapshot or Dynamic Inputs*. --- ## Step 7 — Preview Before You Save Use **Preview and existing series** to see the **next five occurrences** with their exact dates, times and timezone. Check that: - the first date is where you expect it, - the times read correctly in 24-hour format, - the timezone is the one you intended. Then **Save Settings**. --- ## Step 8 — Submit a Parent Entry Submit the form normally, as a user would. If the feed's condition passes, a series starts immediately — but nothing is submitted yet. --- ## Step 9 — Confirm It in Queue Open **GravityOps → Recurring Submissions → Queue** and find the new row. Confirm: | Column | What to check | | --- | --- | | **Form / feed** | The right feed on the right form. | | **Parent entry** | Links to the entry you just submitted. | | **Schedule** | A plain-language summary of the cadence. | | **Next run and window** | The exact target, plus the window it should run inside. | | **Status** | `scheduled · feed active`. | Also glance at the **Worker** card. If it isn't healthy, fix that before relying on the schedule — see *Checking the Worker Before You Rely On It*. --- ## Step 10 — Run It Once, Deliberately Don't wait a day to find out whether it works. Click **Run Next Submission Now**. The plugin submits immediately, consumes the next slot, and keeps the long-term rhythm intact. Then verify: 1. The on-screen result names the outcome and the new child entry ID. 2. The child entry exists and holds the values you expected. 3. The parent entry has a new note naming the feed, the result and a link to the child. 4. **View attempt history** shows the attempt with its target, start, finish, source and outcome. --- ## Step 11 — Let the Worker Do One Now wait for a real automatic run. Compare the attempt's **Target** with its **Started** time — a gap of a few minutes is normal and healthy. --- ## What "First Occurrence" Means A new schedule applies the **interval first**, then the clock time. > A daily feed whose parent is submitted on **September 14 at 01:14**, with a specified time of **01:20**, first runs on **September 15 at 01:20** — not six minutes later. To choose an earlier first run, use **Change next submission** on the series and pick the date and time you want. --- ## If Something Fails 1. Queue shows the outcome and any **validation field IDs** that rejected the submission. 2. Fix the form — a required field with no value is the usual cause. 3. Click **Retry Failed Submission**. A success clears the issue and resets the consecutive-failure count. 4. If you need help, use **Copy Diagnostics** — it produces a redacted report that is safe to send to support. Automatic attempts stop after three consecutive failures by default, so a broken form cannot generate failures forever. --- ## Next Steps - **Choosing Snapshot or Dynamic Inputs** — get this decision right before you scale up. - **Feed Settings** — every field on this screen explained. - **The Queue Screen** — where you'll live once several schedules are running.