Gravity Forms documents that marking an entry Not Spam processes add-on feeds except payment feeds, while notifications are not processed automatically. A restored lead can therefore enter a CRM or webhook path without sending its confirmation, and a manual replay can duplicate work that another operator already completed.
Use this for forms connected to email notifications, CRMs, webhooks, payment add-ons, PDFs, signatures, spreadsheets, Slack, or custom background jobs.
Quick answer
Before marking the entry Not Spam, inventory every configured feed and notification, check whether it already ran, assign a stable entry-level deduplication key, and decide the desired result. After reclassification, verify which non-payment feeds processed, then manually send only required notifications and handle payment actions through the payment system's approved recovery path.
What to check first
- Preserve the original spam note, entry status, form version, submission timestamp, feed configuration, notification configuration, payment fields, and any manual work already performed.
- List every downstream action with its trigger, prior attempt, external record ID, retry behavior, deduplication key, side effect, and owner.
- Decide whether CRM creation, webhook, file transfer, PDF, signature, spreadsheet, and custom jobs should process when the entry is restored.
- Treat payment add-ons and customer notifications separately because Gravity Forms documents that they are not automatically processed in the same way.
- Mark Not Spam in a controlled window, capture feed results, reconcile external systems, send approved notifications once, and record final outcomes.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Preserve entry and feed state | Preserve the original spam note, entry status, form version, submission timestamp, feed configuration, notification configuration, payment fields, and any manual work already performed. | Every feed and notification has one recorded result or intentional skip. |
| Build the downstream matrix | List every downstream action with its trigger, prior attempt, external record ID, retry behavior, deduplication key, side effect, and owner. | External systems contain one expected record for the entry. |
| Choose one deduplication key | Decide whether CRM creation, webhook, file transfer, PDF, signature, spreadsheet, and custom jobs should process when the entry is restored. | No payment action occurred without explicit payment-owner approval. |
| Restore and observe feeds | Treat payment add-ons and customer notifications separately because Gravity Forms documents that they are not automatically processed in the same way. | Customer and administrator messages are current, correctly addressed, and sent once. |
Why this usually happens
- Different feed add-ons use different retry and duplicate-detection behavior.
- A support agent may manually create the CRM lead before the entry is restored.
- Payment workflows carry financial side effects that should not be replayed like a normal CRM feed.
- Notifications can contain expiring links, stale amounts, or recipients that changed after submission.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
entry_id: 9124
original_status: spam
crm_feed: replay
crm_external_id: none
webhook_feed: skip_manual_complete
payment_feed: manual_review
admin_notification: send_once
customer_notification: regenerate
dedupe_key: gf-9124-recovery-v1
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Preserve entry and feed state
- Build the downstream matrix
- Choose one deduplication key
- Restore and observe feeds
- Complete selected manual actions
Decision rule
Replay only the actions needed to reach the intended current state. If an external record, payment, message, or file already exists, reconcile it and skip the duplicate operation.
What to tell the client or owner
Share entry and form IDs, original spam reason, feed matrix, prior attempts and external IDs, deduplication key, reclassification time, automatic feed results, manual messages, payment decision, unresolved actions, and owner.
Production verification checklist
- Every feed and notification has one recorded result or intentional skip.
- External systems contain one expected record for the entry.
- No payment action occurred without explicit payment-owner approval.
- Customer and administrator messages are current, correctly addressed, and sent once.
Mistakes to avoid
- Do not assume Mark Not Spam replays every notification and payment feed.
- Do not manually trigger all feeds before checking external records.
- Do not reuse stale payment or password links.
- Do not remove the spam evidence before understanding the false positive.
Questions teams ask during testing
What does Gravity Forms process after Mark Not Spam?
Its July 2026 documentation says add-on feeds other than payment feeds are processed. Payment feeds are not processed, and notifications are not automatically processed.
Should the customer notification always be resent?
No. Confirm the message remains accurate, useful, correctly addressed, and not already sent through another recovery path. Generate fresh time-sensitive links.
When HandL WP should help
HandL WP can map Gravity Forms feeds, safely recover valid entries, reconcile CRM and webhook side effects, protect payment flows, and prevent duplicate notifications.
If this is active on a production site, recover a valid Gravity Forms spam entry.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Payment feed recovery requires reconciliation
Gravity Forms does not automatically process payment feeds when an entry is marked Not Spam. Use the payment feed manual recovery runbook to search provider state, find customer retries, prevent duplicate charges, obtain approval, and record the final transaction outcome.
Know what Mark Not Spam will process
Build the Gravity Forms Mark Not Spam add-on capability matrix before restoring a live lead. It separates automatic non-payment feeds from payment reconciliation, notification decisions, anti-spam feedback, and unknown custom hooks.
Helpful references