Users report not seeing new activities after connect

[dblock]

User reported installing the bot, connecting, then posting a manual activity and not seeing it sync.

#<User _id: 5e937eeb0661e5235e9d5bca, created_at: 2020-04-12 20:49:47 UTC, updated_at: 2020-04-14 12:51:27 UTC, connected_to_strava_at: 2020-04-12 20:49:56 UTC ...>

irb(main):014:0> u.connected_to_strava_at
=> Sun, 12 Apr 2020 20:49:56 +0000
irb(main):015:0> u.connected_to_strava_at.to_i
=> 1586724596

The activity that the user claims was created after:

u.strava_client.athlete_activities(after: u.connected_to_strava_at.to_i)
=> []

The manual activity was created at 2020-04-12 20:46:19 UTC, which is 1586724379, delta 217, so assuming the event was created earlier there's a delta in clocks being assigned to the activity when created manually.

[CristhianGarzon]

In our company, we also want to connect new users to be able to receive the notifications, we successfully connected and received notifications from the first 3 users, however, we've got another 3 connected afterwards (in total 6), and somehow we didn't receive their notifications.

is it related to the subscription plan, or is there another issue?

[dblock]

In our company, we also want to connect new users to be able to receive the notifications, we successfully connected and received notifications from the first 3 users, however, we've got another 3 connected afterwards (in total 6), and somehow we didn't receive their notifications.

is it related to the subscription plan, or is there another issue?

There's probably another issue. Email me dblock at dblock dot org with some details on team name, names of users that didn't receive notifications and a link or two of activities that you expected them to receive (check that those activities were created after the user(s) connected).

[dblock]

Recent activities on the edge of when a new user connects continue to confuse people. In the above example a user connected the bot on Mon, 28 Sep 2020 07:46:11 UTC. The most recent activity they had in Strava was 2020-09-28 07:36:56 UTC, and had a duration of 776s, which put it at 2020-09-28 07:49:52 UTC end, after the user connected the account. In https://github.com/dblock/slack-strava/commit/9b7515da17772c5f2c83c92e1c2e3d3e07328505 I've changed this to include 8 hours of prior activities.

[CristhianGarzon]

Thanks Daniel,

We’ve got the first alerts from them

On Tue, 29 Sep 2020 at 12:19 am, Daniel Doubrovkine (dB.) @dblockdotorg < notifications@github.com> wrote:

Recent activities on the edge of when a new user connects continue to confuse people. In the above example a user connected the bot on Mon, 28 Sep 2020 07:46:11 UTC. The most recent activity they had in Strava was 2020-09-28 07:36:56 UTC, and had a duration of 776s, which put it at 2020-09-28 07:49:52 UTC end, after the user connected the account. In 9b7515d https://github.com/dblock/slack-strava/commit/9b7515da17772c5f2c83c92e1c2e3d3e07328505 I've changed this to include 8 hours of prior activities.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dblock/slack-strava/issues/82#issuecomment-700037636, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEI7HDPY3VUFCVOYESS2R43SICLO7ANCNFSM4MHY46AQ .

-- Regards,

Cristhian Garzon +61 404170366 https://www.linkedin.com/in/cristhian-garzon/ Master of IT - Spatial (2018) The University of Melbourne