This article covers the most common reasons XML feed syncs fail and how to resolve them.
Diagnosing the issue
Go to Jobs → Feeds.
Click the feed with Error status.
Go to the Sync logs tab.
Click the most recent failed sync to read the error details.
Common errors and fixes
"Feed URL unreachable"
Cause: Wonderkind could not connect to the feed URL. This happens when:
The URL is incorrect or has changed
The server hosting the feed is down or blocking the request
The URL requires authentication that Wonderkind cannot provide
Fix:
Open the feed URL in a browser to verify it works.
If the URL has changed, go to Feed Settings → Feed URL and update it.
If the URL requires a login or IP allowlist, contact your Wonderkind administrator to configure access.
"Invalid XML structure"
Cause: The feed response was received but could not be parsed as valid XML.
Fix:
Open the feed URL in a browser and inspect the raw content.
Validate the XML using an online validator (e.g., xmlvalidation.com).
Common issues: unclosed tags, special characters not escaped (
&should be&), BOM character at the start of the file.Contact your ATS or feed provider to fix the XML formatting.
"Field mapping error: [field name] not found"
Cause: A required field (usually title, location, or application URL) was not found at the expected XML element path.
Fix:
Open the feed URL in a browser and inspect the XML structure.
Go to Feed Settings → Field Mappings.
Update the mapping to point to the correct XML element containing the missing field.
Save and trigger a manual sync.
"Jobs imported: 0"
Cause: The sync completed successfully but found no jobs. Possible reasons:
The feed is empty
All jobs match the deactivation condition (e.g., all jobs have
<status>closed</status>)The feed uses pagination and only the first page was fetched (no jobs after page 1 in your mapping)
Fix:
Inspect the feed XML to confirm jobs are present and not marked as closed/inactive.
If the feed uses pagination, contact Wonderkind support to configure paginated feed handling.
"N jobs deactivated" (unexpected)
Cause: Jobs that were in the previous sync are no longer in the current feed. This is expected behavior for roles that have been filled or removed from your ATS.
If the deactivation was unexpected:
Inspect the feed to see if those job IDs are still present.
Check if the feed URL has changed or if the feed provider had a data issue.
If needed, re-activate the jobs manually from the Jobs page.
Manual sync after fixing
After updating field mappings or fixing the feed source:
Go to Jobs → Feeds.
Click ⋯ → Sync now on the feed.
Watch the sync log for success confirmation.
Preventing future issues
Monitor the Feed Health dashboard regularly (Jobs → Feeds overview).
Enable email notifications for Feed errors in your notification settings.
When your ATS updates or migrates, check feed URLs and XML structure before the migration completes.
Related articles
Setting Up an XML Feed
Feed Sync & Health Monitoring
