title: Drive app data and rate limits
body: <p>We've been using the older version of the api for a while, which required explicit data push back and forth to drive.  We ran into issues on app data restore when current users with lots of data tried to restore.  It was an issue we couldn't reproduce locally, but we got a couple logs from people, and there was some kind of 500 error.  In retrospect, it may have been a rate limit, as we were downloading lots of data in one chunk.</p>
  
  <p>Anyway, moved to the new api tied to google play services.  We let that handle app data, and use the api to handle data store and retrieval.  In testing it seemed super smooth, and we didn't need to worry about backup explicitly, which sounds nice.</p>
  
  <p>We're getting reports from users about missing data.  I think I've finally replicated it.  In a test account I've generated 1k-2k files.  On the device where the data was generated, things are OK.  On a new device, not all data shows up.  In the log, I get this:</p>
  
  <p>E/SyncScheduler﹕ Ignoring sync request:  rate limited (on connection limit)</p>
  
  <p>and...</p>
  
  <p>E/SyncScheduler﹕ Ignoring sync request:  rate limited (normal limit)</p>
  
  <p>that.  More of the latter.</p>
  
  <p>Now that its going through play services, its kind of a black box.  The status from the call seems to be SUCCESS, but the call to drive (remote) is clearly failing.</p>
  
  <p>Is there a per-user daily type of limit?  If play services is dealing with drive directly, is there a way to figure out that we're over the limit?  Right now, it just looks like the user has lost their data, but the app thinks everything is OK.  Ideally the user rate limits could be raised, or somebody can tell me what we're doing wrong.  We're currently in a minor nightmare situation with customer support.</p>