Introduction
When a feed isn’t processing as expected, follow these steps to identify and resolve the issue.
Prerequisites
Before debugging feeds, ensure logging is enabled in Gravity Forms.
Debugging Steps
Test the Form
Submit a test entry that should trigger the feed. This generates fresh log data to review.
Note: Use realistic test data that matches your feed’s conditional logic and field requirements.
Example: User Registration feed failing due to missing required fields.
2026-02-12 9:36:44.261164 - DEBUG --> Gravity_Forms\Gravity_Forms\Async\GF_Background_Process::update(): Batch wp_gf_userregistration_feed_processor_batch_cd5f123d2385d4525ec2b4882e5b78 updated. Tasks remaining: 1.
2026-02-12 9:36:44.261204 - DEBUG --> Gravity_Forms\Gravity_Forms\Async\GF_Background_Process::handle(): Processing task 1. Attempt number: 1.
2026-02-12 9:36:44.261233 - DEBUG --> GF_Feed_Processor::task(): Preparing to process feed (#67 - Test - User Registration) for entry #536.
2026-02-12 9:36:44.263444 - DEBUG --> GF_Feed_Processor::task(): Starting to process feed (#67 - Test - User Registration) for entry #536. Attempt number: 1.
2026-02-12 9:36:44.263484 - DEBUG --> GF_User_Registration::process_feed(): form #50 - starting process_feed().
2026-02-12 9:36:44.263865 - DEBUG --> GF_User_Registration::process_feed(): aborting. user_login or user_email are empty.
2026-02-12 9:36:44.265029 - ERROR --> GF_Feed_Processor::task(): Aborting. Error occurred during processing of feed (#67 - Test - User Registration) for entry #536: user_login or user_email are empty.
Review the Logs
After testing, examine the logs for details:
- Go to Forms > Settings > Logging.
- Click View Logs next to the add-on.
- Locate your test entry.
- Review any error messages or processing details.
Check the add-on Settings
Verify the add-on’s general connection settings:
- Confirm API credentials are valid and active.
- Check that the add-on is properly connected to the third-party service if applicable.
- Look for any authorization or connection errors in the add-on settings page.
Review Feed Conditional Logic
If your feed uses conditional logic, verify it’s configured correctly:
- Navigate to Forms > [Your Form] > Settings > [Add-on Name]
- Select the feed.
- Review the Conditional Logic section.
- Confirm the conditions match your test entry’s submitted data.
Verify Field Mappings
Ensure all fields are correctly mapped within the feed:
- Review each field mapping in the feed configuration.
- Confirm required fields for the third-party service are mapped.
- Check that field types are compatible (e.g., email fields to email, numeric to numeric)
- Look for any unmapped required fields.
Common Feed Issues
| Problem | Possible Causes | Solution |
|---|---|---|
| Feed not processing at all | Conditional logic not met | Review conditional logic settings and verify test entry meets all conditions |
| Add-On disconnected | Check the add-on settings page for connection status and re-authorize if needed | |
| Feed is inactive | Edit the feed and ensure it’s set to “Active” | |
| Entry marked as spam | Feeds are not processed for spam entries | |
| Feed processing but failing | Invalid API credentials | Verify API keys/credentials in add-on settings are current and correct |
| Third-party service issue | Check the service’s status page for outages or maintenance | |
| Missing required fields | Review field mappings, ensure all required fields for the service are mapped | |
| Rate limiting | Check logs for rate limit errors, you may need to wait or upgrade your service plan | |
| Feed processing with unexpected results | Incorrect field mappings | Review all field mappings for accuracy |
| Field type mismatch | Ensure field types are compatible (e.g., email to email, number to number) | |
| Data format issue | Verify data formats meet service requirements (date formats, phone number formatting, etc.) | |
| Conditional logic partially met | If using “Any” logic, check which conditions are actually being met |
Reprocessing Feeds
If you need to process feeds for an entry that wasn’t processed or failed, you can use the third-party plugin Feed Forge, which allows you to reprocess feeds for existing entries.
After Debugging
Once troubleshooting is complete, make sure you disable logging. Go to Forms > Settings and click the link to delete the files and disable logging. Disabling logging will delete the log files.
Note: Log files may contain personal and sensitive information. Don’t leave logging enabled or log files on your server after completing your investigation.
Resources
- Troubleshooting Form Submission Performance
- Troubleshooting Background (async) Processing Issues
- Working With Multiple Feeds
- Enabling Conditional Logic for Feeds
Disclaimer: Third-party services, plugins, or code snippets that are referenced by our Support documentation or in Support Team communications are provided as suggestions only. We do not evaluate, test or officially support third-party solutions. You are wholly responsible for determining if any suggestion given is sufficient to meet the functional, security, legal, ongoing cost and support needs of your project.
Feedback, feature, and integration requests, and other functionality ideas can be submitted at http://forms.roadmap.gravity.com/.