Ask the Community
Groups
Google Contacts 99999 Error - Connect IT Community | Kaseya
<main> <article class="userContent"> <p aria-level="2"><strong>Background</strong><span data-ccp-props="{"201341983":0,"335559738":40,"335559739":0,"335559740":259}"> </span></p> <p><span data-contrast="auto">On November 23</span><span data-contrast="auto">rd</span><span data-contrast="auto">, 2021, Google officially </span><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fdevelopers.google.com%2Fpeople%2Fcontacts-api-migration"><span data-contrast="none">deprecated the legacy</span></a><span data-contrast="auto"> “Contacts API”. This API has been utilized since the beginning by Spanning to meet your organization’s data protection needs for contacts. The Contacts API has been replaced by the new “</span><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fdevelopers.google.com%2Fpeople"><span data-contrast="none">People API</span></a><span data-contrast="auto">”</span><span data-ccp-props="{"201341983":0,"335559739":160,"335559740":259}"> </span></p> <p><span data-contrast="auto">Spanning proactively planned, engineered, and deployed new code to prepare for this migration in advance. Upon switching to this new API, we realized that it was not delivering the same performance as we used to achieve with the Contacts API. We believe in ensuring our standards are met and consistent. The engineering team has conducted a full investigation into why this performance degradation has occurred and has identified additional improvements post-migration to bring the performance of our contacts back up to our high standards.</span><span data-ccp-props="{"201341983":0,"335559739":160,"335559740":259}"> </span></p> <p aria-level="2"><strong>What is the impact? </strong></p> <ul><li data-leveltext="" data-font="Symbol" data-listid="1" aria-setsize="-1" data-aria-posinset="1" data-aria-level="1"> <span data-contrast="auto">After November 23</span><span data-contrast="auto">rd</span><span data-contrast="auto">, 2021, customers may notice that contacts backups may be taking an unusually long amount of time to complete</span><span data-ccp-props="{"201341983":0,"335559739":160,"335559740":259}"> </span> </li> <li data-leveltext="" data-font="Symbol" data-listid="1" aria-setsize="-1" data-aria-posinset="2" data-aria-level="1"> <span data-contrast="auto">Customers may notice an unusually large number of contacts backup attempts returning 99999 errors “Too many requests”</span><span data-ccp-props="{"201341983":0,"335559739":160,"335559740":259}"> </span> </li> </ul><p aria-level="2"><strong>What is not impacted? </strong></p> <ul><li data-leveltext="" data-font="Symbol" data-listid="1" aria-setsize="-1" data-aria-posinset="3" data-aria-level="1"> <span data-contrast="auto">There is no impact to contacts backed up before November 23</span><span data-contrast="auto">rd</span><span data-contrast="auto">, 2021, by the legacy Contacts API or any contacts successfully backed up by the People API after November 23</span><span data-contrast="auto">rd</span><span data-contrast="auto">, 2021,</span><span data-ccp-props="{"201341983":0,"335559739":160,"335559740":259}"> </span> </li> <li data-leveltext="" data-font="Symbol" data-listid="1" aria-setsize="-1" data-aria-posinset="3" data-aria-level="1"> <span data-contrast="auto">There is no impact on the data at rest of any other workload (Drive, Mail, Calendar, etc.)</span><span data-ccp-props="{"201341983":0,"335559739":160,"335559740":259}"> </span> </li> <li data-leveltext="" data-font="Symbol" data-listid="1" aria-setsize="-1" data-aria-posinset="3" data-aria-level="1"> <span data-contrast="auto">There is no impact on the ability to perform a contacts restore with the new People API</span><span data-ccp-props="{"201341983":0,"335559739":160,"335559740":259}"> </span> </li> </ul><p aria-level="2"><strong>What have we done so far?</strong><span data-ccp-props="{"201341983":0,"335559738":40,"335559739":0,"335559740":259}"> </span></p> <p><span data-contrast="auto">In addition to following best practices and standards like incremental back-off logic, we have worked with our ISV support partners to raise our app’s API capacity to meet the rigorous needs of our customers. In addition to the output of those improvements we have implemented:</span><span data-ccp-props="{"201341983":0,"335559739":160,"335559740":259}"> </span></p> <ul><li data-leveltext="-" data-font="Calibri" data-listid="3" aria-setsize="-1" data-aria-posinset="0" data-aria-level="1"> <span data-contrast="auto">More efficient querying and processing of contacts data via the API</span><span data-ccp-props="{"201341983":0,"335559739":160,"335559740":259}"> </span> </li> <li data-leveltext="-" data-font="Calibri" data-listid="3" aria-setsize="-1" data-aria-posinset="0" data-aria-level="1"> <span data-contrast="auto">Additional improvements to our logic to further reduce the number of 99999 errors from the API</span><span data-ccp-props="{"201341983":0,"335559739":160,"335559740":259}"> </span> </li> </ul><p aria-level="2"><strong>What are Spanning’s next steps and when can we expect a resolution? </strong></p> <p><span data-contrast="auto">We believe customers should already begin seeing improvements in performance. Spanning is working on a solution to utilize delta queries for Google Workspace People API to retrieve only changed contacts.</span><span data-ccp-props="{"201341983":0,"335559739":160,"335559740":259}"> </span></p> </article> </main>