Intermittent failures on the search endpoint for Google accounts

Description

  • The /search sub-endpoint runs a full-text search proxied to the account's provider. Because of this, search results may take longer to return or might error out sometime due to the issue on the provider side.

Common errors

  • HTTP 429, User-rate limit exceeded:

    This 429 error means that the user has exceeded the number of requests allowed in a given time period. This error is often caused by a high volume of requests being sent, which can lead to rate limiting.

    To resolve a 429 error, you can implement a retry mechanism that waits for a certain amount of time before retrying the failed request. Nylas recommends using exponential backoff to avoid sending a large number of requests at once.

    For more information please refer to the following article: Gmail API - Resolve errors - Retry failed requests to resolve errors

     

  • HTTP 503 Gmail service is temporarily unavailable:

    This 503 HTTP error means that the Gmail API is temporarily unavailable. This error can occur due to maintenance, updates, or other issues with the API's servers.

    To resolve a 503 error, you should wait and retry the failed request after a certain amount of time. Nylas recommends using exponential backoff to avoid sending a large number of requests at once.

    For more information please refer to the following article: Gmail API - Resolve errors - Retry failed requests to resolve errors


    References

  • Nylas Search endpoints

Updated

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.