Username suddenly not found?

[ToothyDev]

I had this set up for quite some time with wakatime and it worked just fine. However, when I checked today, it broke, saying "Wakatime user not found". I have changed absolutely nothing about my wakatime nor the link in my profile, here is the link I used:
https://github-readme-stats.vercel.app/api/wakatime?username=ToothyDev&theme=radical&hide_border=true&show_icons=True&layout=compact

And here is my wakatime link: https://wakatime.com/ToothyDev

[qwerty541]

Check this discussion: #1825
I hope it will help you

[ToothyDev]

My profile is as public as it goes and more than 4h have passed, it still doesn't show

[qwerty541]

I see that a lot of users currently have same issue. Most likely, this does not depend on you and no action is required from you. I think that merging #2670 will resolve that,

[qwerty541]

Or you can manually set &range=all_time option to fix it now.

[rickstaa]

It should be fixed now that #2662 was merged.

[AmodeusR]

I'm facing the same issue. The "&range=all_time" didn't work for me. It seems I'll need to wait for the fix.

[rickstaa]

It should be fixed now that #2662 was merged.

[AmodeusR]

My profile is still showing the error.

[nemchik]

Make sure you have Display code time publicly set to All Time at https://wakatime.com/settings/profile

If you prefer your image to display a shorter range, you can use &range=last_year or &range=last_7_days but the profile setting has to be at least enough to include the range you want to use. Personally I leave the profile setting on All Time and use the image with &range=last_7_days.

[rickstaa]

@AmodeusR the problem still wasn't fixed. Will be after #2707 is merged.

[hakula139]

According to the doc:

range – Request a range different from your WakaTime default, e.g. last_7_days. See WakaTime API docs for a list of available options. (YYYY-MM, last_7_days, last_30_days, last_6_months, last_year, or all_time). Default all_time.

And I've found if I set a range the SAME as my WakaTime settings here (Display code time publicly), e.g. &range=last_7_days (instead of &range=all_time), it solves my issue.

[rickstaa]

It should be fixed now that #2662 was merged.

[hakula139]

It should be fixed now that #2662 was merged.

This PR is not related to this issue, as you may see the problem still exists here, but fixed by adding a range param like this.

[rickstaa]

Your correct the pull request only resolved the issue for some users (see #2698 and #2671).