title: New Google Spreadsheet formula results different than what I see, importrange function unstable
body: <p>I have a 200k cell database in New Google sheets. I'm running <code>QUERY()</code> in the same spreadsheet but in another sheet.</p>
  
  <p>The results I get from <code>QUERY()</code> is perfectly fine. The problem is: when I try to use the resulting queried data in another sheet, the resulting data is not what I see from the <code>QUERY()</code>. I only see a portion of it. This happens both when I use <code>importrange()</code> and when I use Google app script code to replace <code>importrange</code>. </p>
  
  <p>When using code and I <code>.getValues()</code> the range, the data fetched is already not what it looks like in the <code>QUERY</code> function on the original sheet. So that's why I'm saying the actual result from <code>QUERY</code> is different from what I see.</p>
  
  <p>The <code>QUERY</code> result from what I see is correct. The data set from <code>importrange()</code> or <code>.getValues()</code> is incorrect. This just happened suddenly. Before everything was working fine. It started this Friday (March 21, 2014) night EST.</p>
  
  <p>Wondering if anybody else is having this same problem.</p>
  
  <p>Edit: I've also tried the <code>myimportrange()</code> custom code provided by ahab as a work around. I get the same result as <code>importrange()</code>. I've exhausted what I can try I think. Might be a Google bug?</p>
  
  <p>Edit 3/24/14: It seems to only a problem on formulas. I have a different part of the spreadsheet that was also not importing all of the values, but for that portion i pasted values because it will not change any more, and the problem resolved itself.</p>
  
  <p>It seems like the formula calculates and I can see it but Google's server has a different number for that cell.</p>
  
  <p>edit 3/24/14 10am EST: Things all came back without me doing anything. I think it was a Google issue. They must have turned something off over the weekend and turned it back on when the engineer got into the office today. Should I just delete this question? Moderator?</p>
  
  <p>edit 3/28/14 10pm EST: it's happening again. This time the <code>QUERY()</code> function not producing the correct results.</p>
  
  <p>edit 4/2/14: This problem carries over to other formulas (simple formulas) </p>
  
  <p>edit 4/7/14: This seems like a recurring problem over the weekends (US time zone)</p>
  
  <p>edit 4/23/14: latest cycle of <code>importrange</code> down started Good Friday, <code>importrange</code> works again now.</p>
  
  <p>edit: I have a more accurate description of the error:
  So let's say i have a spreadsheet <code>foo</code>. In cell <code>A1</code>, <code>sheet1</code> in spreadsheet <code>foo</code>, is a formula that returns value <code>X</code>. value <code>X</code> is the correct value, but since value <code>X</code> depends on all these different calculations (such as a query, which is blank at load) from inside the spreadsheet, when you first open/load the spreadsheet, the initial value is <code>Y</code>. Only after about 30 seconds to 1 minute does the value (after calculating what looks like 3-4 times) settle correctly to value <code>X</code>. Every time i hit reload on the spreadsheet, the value gets reset to value <code>Y</code>, and it takes 30 seconds to 1 minute to arrive at the correct value <code>X</code>.</p>
  
  <p>Now i have another spreadsheet <code>bar</code>. In <code>bar</code>, i'm importing the range <code>sheet1!A1</code> from spreadsheet <code>foo</code>. However, value <code>Y</code> shows up, even though value <code>X</code> is displayed in <code>foo</code>. So <code>bar</code> is only loading the initial value but not the calculated and most recent value <code>X</code>. </p>
  
  <p>This phenomena has been ongoing since I started using the new sheets. Sometimes it imports correctly and imports <code>X</code> from <code>foo</code>, other times it imports <code>Y</code> from <code>foo</code>. And i've done absolutely nothing. It seems to be unstable. Sometimes it is able to import the correct value, sometimes not.</p>