How does the import & build process works?

[wardwygaerts]

I have everything working, started the import and ran the build command.
I now have 32 activities in my dashboard, but it's still importing (1268 tog go..). When I refresh my dashboard, I don't see the number of activities increasing. So how is this working?
I also know I can change the cron to have more control, but how is the import.build working by default? When will an activitiy be visible after Strava received it?

Nice app btw! :)

[robiningelbrecht]

When I refresh my dashboard, I don't see the number of activities increasing. So how is this working?

Everytime data is imported, you need to run the build command. That command updates the HTML pages

When will an activitiy be visible after Strava received it?

When you run the import command. So by default once a day

Maybe I need to explain this more clearly in the docs? dunno

[robiningelbrecht]

[wardwygaerts]

In the troubleshooting FAQ I found this:
By default, the app will only import 250 new activities per run to avoid hitting rate limits. You can change this number in the .env file. If you still hit the daily rate limit, the app will automatically import the remaining activities the next day(s).

But if I understand correctly I need to the schedule the import & build myself?

[robiningelbrecht]

@wardwygaerts no, the app will automatically import and build based on the schedule you have set. By default this is once a day:

[wardwygaerts]

oh yes, offcourse, missed that entry...

It will only import new activities I suppose? I restarted the import command and noticed it also updated the already imported activities. Doesn't this count for the API calls?

[robiningelbrecht]

@wardwygaerts No, updates do not count for extra API calls ;).

[wardwygaerts]

Thanks! everything is clear.