Google Cloud Talent Solution v3匹配Jobs缺失问题求助

Google Jobs API v3: matchingJobs Returns None But totalSize Is Correct #

Hey there, you’re not alone in running into this issue! Over the last few hours, I’ve seen multiple similar reports pop up in developer communities. Let’s walk through some possible fixes and things to check:

• Inspect the full response payload: Even though totalSize shows the right count, log the entire response object to see if job data is nested under a different key—some users noticed their results were under jobs instead of matchingJobs recently, likely due to an unannounced minor schema tweak from Google.
• Double-check your request parameters: Did you make any changes to your search() call lately? Things like an invalid pageToken, pageSize set to 0, or a filter that accidentally hides all visible results (while still counting them in totalSize) can trigger this. Try testing with a minimal request (just your project ID and a basic query) to see if matchingJobs returns normally.
• Verify API service status: Even though the API accepts new jobs, there might be a partial degradation affecting search result formatting. Check the Google Cloud Status Dashboard for any active issues with the Jobs API.

What Other Users Are Doing #

Several developers who faced this issue mentioned that rolling back to an older version of the client library (if you’re using one) temporarily fixed the problem. Others reached out to Google Cloud Support with their project ID and a sample request/response, which helped escalate the issue for a quicker resolution.

If none of these steps work, sharing a redacted version of your search() request parameters could help the community narrow down the exact cause.

内容的提问来源于stack exchange，提问作者Carl