webhook events missing; is non-expired access token required?

I’m wondering, does Strava stop sending webhooks events for an athlete if the athlete’s access token needs to be refreshed?

To my knowledge, no. As long as the athlete still has your app authorized you’ll receive the webhook calls. I’ve never had to add anything to my app to specifically refresh tokens, it instead happens naturally as part of retrieving activity data once a webhook comes in (or the user logs on to my site).

The one thing I can think of is public vs private activities. If they haven’t authorized your app to view private activities you won’t get webhook calls for any activity set to “only me” or “followers”

Ok thanks ​@ActivityFix yeah it’s pretty weird; the activities are public I can see them without friending the athlete, but I didn’t receive the events. I refreshed the token and now I am getting their events again.

I’m going to set up some more robust testing/logging to make sure my endpoint isn’t dropping things.

Hi ​@renschler , I'm trying to figure out why I'm not receiving activity events on my webhook. What do you mean by "I refreshed the token"? 

I have the same issue as the following post:

My scenario might be different than yours. I am getting most of my events from most of my atheletes, I’m just finding that sometimes events for particular athletes stop being delivered and it’s unclear why.

The way the API works, you have an temporary access token and then a refresh token used to refresh you access token. The question I’m posting here is “do I have to keep the access token up to date in order to receive webhook events for an athlete”. In theory it shouldn’t work like that, but I’m having trouble figure out why sometimes I lose events for athletes even though my app is still authorized.

My endpoint has a theoretical limit of 10,000 RPS so I don’t think I’m dropping anything from Strava but I am planning on adding more logging to see.