Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Every now and then I start getting “Unexpected. Please try again.” for ANY query i try. It usually gets better a bit later but the rate at which it appears is very worrying.
What can I do when this happens?
here are some job ids:
job_648552a52f3046c5b2df9300a31d4693
job_4af4184725974c3fb38e0ded96b776c9
If you get this response, please let us know because it indicates a bug in BigQuery.
Looking at the jobs in question, this is a race condition where we mark the import complete before it has completely replicated to all datacenters, and the query hits a different datacenter. I’ve filed a bug and we’re working on a fix.