If you are using a job importer (XML feed) you might encounter a variety of error messages. Job imports can be complex, and errors can happen for a variety of reasons. This article will provide you with an overview of the most common error messages and the reasons for them. Whether you are setting up a new job importer or already using an importer, read on to learn more about job importers.
Empty feed
This error can happen in different cases:
| Case | Description |
|---|---|
| The source file is empty | The source file has no job updates (changes). |
| The mapping has an issue with values |
When a feed item is processed and the field mapping is not correct such an error can appear. |
| The file URL is empty |
When processing the XML feed and the XML URL is empty. |
| Cannot find a related entity reference |
During the processing of the feed item when the reference field cannot find a related reference value in the XML file. |
| Issues during parsing (bad chars, incorrect mapping, etc.) |
During parsing of the XML feed, there are issues (encoding issues, dom, bad chars, ...). |
| Issues with preparing values for the GEO-field feeds mapper. |
If there are issues with mapping GEO-field values, such as when the Latitude and Longitude are not paired correctly, it may be necessary to modify the XML file and import it again. |
Operation timed out
This error occurs when the client-server is responding slowly or not responding at all while the importer is trying to fetch data from the XML feed (original source). In some cases, the issue may be related to the XML file size.
UTF8 encoding is longer than the max length
This error typically occurs when the amount of imported data exceeds the maximum limit allowed by the SOLR data type for a specific field. For instance, if a job description contains more than 33,000 characters, the large text can trigger this issue during the import process. This problem can occur for other fields as well.