Proximity API returns '503 - Service Unavailable' quite frequently

[firecast]

We (Beaconstac) are seeing an increasing number of Proximity API requests returning '503 - Service Unavailable' errors.

For example: <HttpError 503 when requesting https://proximitybeacon.googleapis.com/v1beta1/beacons/3!5dc33487f02e477d4058ac233f25592d/attachments:batchDelete?projectId=beaconstac-1043&alt=json&namespacedType=com.google.nearby%2F%2A returned "The service is currently unavailable.">.

It seems occur at random intervals where all the requests to the API fail at the same time and then start back up normally after a few seconds or so.

Also, we'd like to know when this API will be available in PRODUCTION, as it appears to still be in beta at the moment.

We created a google issue here where the engineer redirected us to file an issue here.

[peetsasaki]

Thank you for raising this issue.

While we investigate the issue on our side, It might be a good idea to implement several delayed retries in your client (which is generally a good idea for network calls anyway). Since you've found that these periods of error responses last a few seconds, that should stop the impact on your system.

re: beta vs. prod: We don't have anything to announce about this at this time.