Since there has been no follow-up to this, I’m going to mark this as resolved, but first I’m going to add this:
We discovered an issue in Matador Jobs (Pro and Lite) 3.4.x where a failure (due to bad configurations for Google Indexing API) may interrupt the saving of the job post metadata, which as of 3.4.0 included a datapoint that was used to identify when an imported job was already in the system (and thus should result in a revision/update) or wasn’t in the system (and thus should result in a new job being saved).
While we cannot fix the cause of the issue, which is a misconfiguration in the Google Indexing API credentials, we did create two fixes for Matador coming in the 3.5.0 release next week, they are:
– Save the “duplicate check” data point immediately on job save and before from the normal meta flow, which should prevent a failure in that process from preventing the duplicate check data point from being saved.
– Handle failures with Google Indexing API calls more gracefully, so they do not interrupt otherwise successful routines.
In a future release, likely our 3.5.1 release, we will also include a better notice for site operators whose Google Indexing API credentials are not working.
That said, it is possible Paul’s answer helped out already. I’m marking this as resolved.