What does google's OAuth refresh_token limit mean?

Question

Google

In one of the projects, authorization from Google was required to access the user's calendar.
The access_token lifetime is only 1 hour. I read about refresh_token, with which you can get a fresh access_token.
But in the Google documentation there is this footnote:

There is currently a limit of 50 refresh tokens per user account per client. If the limit is reached, creating a new token automatically invalidates the oldest token without warning. This limit does not apply to service accounts.
There is also a larger limit on the total number of tokens a user account or service account can have across all clients. Most normal users won't exceed this limit but a developer's test account might.
If you need to authorize multiple programs, machines, or devices, one workaround is to limit the number of clients that you authorize per user account to 15 or 20. If you are a G Suite admin, you can create additional admin users and use them to authorize some of the clients.

Does this mean that I cannot get a fresh access_token for one client more than 50 times? That is, if the data is updated once an hour, then after 2 days the user must re-authorize?
How to be in this case? Is there a way to authorize a user and not worry about it anymore, and let the application do its thing?