Google Apps Script Integration Failing

1

Project Name (if applicable, otherwise just type n/a)

n/a

Question

Dear Team,

Following the recent update on the Epicollect5 side, all Google Apps Script integrations used to sync data with Google Sheets have become completely non-responsive across multiple projects.

The consistent error returned is:
“Authentication Error: Address unavailable”

These integrations have been working reliably for over two years. However, since the update implemented last Saturday, all authentication requests are failing.

At this point, we are unable to fetch even a single record of data from any project.

I have already updated my Google Apps Script to comply with the new API limits (including token usage and request rate), but the issue persists.

This suggests a problem with the authentication endpoint or a broader API access change.

Kindly confirm:

Whether the authentication endpoint is currently operational
If there have been breaking changes to API authentication
Any required updates on the client side

Your urgent support is needed to restore functionality.

Best regards,

I confirm I have read the User Guide at docs.epicollect.net

on

I confirm I have searched for an answer in this community.

on

I confirm I have tried asking the same question to Perplexity AI with the tag #epicollect5, but it did not help.

on

2

We would like to clarify that there were no updates or changes deployed on the Epicollect5 platform last Saturday that would affect API authentication or Google Apps Script integrations.

To help us investigate further, could you please provide a bit more detail? In particular:

  • The name(s) of the affected project(s)

  • The exact API endpoint(s) being requested

  • The IP address(es) from which the requests are originating

  • A sample of the request/response (including timestamps, if possible)

From what you’ve described, it is possible that our anti-abuse mechanisms may have been triggered, which can result in temporary blocks and authentication errors such as the one you’re seeing. This is typically due to a high volume or pattern of repeated requests.

Once we have the additional information above, we’ll be able to look into this more precisely.

To help avoid similar issues in the future, we also recommend considering the new local export workflow recently introduced in our mobile apps.

This allows you to export data & media directly from the mobile app and upload it directly to your cloud service of choice, eliminating reliance on Epicollect5 servers.

You can find more details here: Beta Updates | Epicollect5 User Guide