Remote config reads quota for server

[Piotr Prus]

Yesterday(29.11) we had a major issue on our backend that uses remote config. Our services where getting error while trying to get remote config template. It turned out we reached the quota limit, but what is really weird is that we reached the reads quota, that is super low (60 per minute) and it is for end users, not for backend. The backend quota should use the fetches function and the limit there is 4 000 000 per minute. How is that possible that we reached the reads quota? Is that means our services for some reason are using reads, not fetch? 
I saw firebase has now the server remote config params but we did not migrate yet. Can that be an issue that our server is using client remote config params?
On backend we are using firebase admin https://www.npmjs.com/package/firebase-admin and function:
`await admin.remoteConfig().getTemplate();`
maybe here is the mistake somewhere?

[Joe Spiro]

Hello,

This use of admin.remoteConfig().getTemplate() is intended for template modifications only and not for serving templates to end users.

The right function to use is admin.remoteConfig().getServerTemplate() which qualifies for much higher quota but that will require migrating  to Server-side RC. Detailed explanation.

Regards.

Joe