pushing 1 heartbeat(s) to queue after error: won't send heartbeat due to backoff without proxy

[hidesec]

Wakatime is unable to track my coding time. Here is the error message shown in the log:

{"level":"debug","now":"2025-05-23T10:58:40+07:00","caller":"heartbeat/sanitize.go:34","func":"github.com/wakatime/wakatime-cli/cmd/heartbeat.initHandleOptions.WithSanitization.func11.1","message":"execute heartbeat sanitization","version":"v1.115.3","os/arch":"linux/amd64","file":"/home/hans/.wakatime/wakatime.log","time":1747972714.2192502,"plugin":"vscode/1.100.2 vscode-wakatime/25.0.3","lineno":17890} {"level":"debug","now":"2025-05-23T10:58:40+07:00","caller":"remote/remote.go:110","func":"github.com/wakatime/wakatime-cli/cmd/heartbeat.initHandleOptions.WithCleanup.func12.1","message":"execute remote cleanup","version":"v1.115.3","os/arch":"linux/amd64","file":"/home/hans/.wakatime/wakatime.log","time":1747972714.2192502,"plugin":"vscode/1.100.2 vscode-wakatime/25.0.3","lineno":17890} {"level":"debug","now":"2025-05-23T10:58:40+07:00","caller":"offline/offline.go:63","func":"github.com/wakatime/wakatime-cli/cmd/heartbeat.SendHeartbeats.WithQueue.func2.1","message":"execute offline queue with file /home/hans/.wakatime/offline_heartbeats.bdb","version":"v1.115.3","os/arch":"linux/amd64","file":"/home/hans/.wakatime/wakatime.log","time":1747972714.2192502,"plugin":"vscode/1.100.2 vscode-wakatime/25.0.3","lineno":17890} {"level":"debug","now":"2025-05-23T10:58:40+07:00","caller":"backoff/backoff.go:45","func":"github.com/wakatime/wakatime-cli/cmd/heartbeat.SendHeartbeats.WithBackoff.func3.1","message":"execute heartbeat backoff algorithm","version":"v1.115.3","os/arch":"linux/amd64","file":"/home/hans/.wakatime/wakatime.log","time":1747972714.2192502,"plugin":"vscode/1.100.2 vscode-wakatime/25.0.3","lineno":17890} {"level":"debug","now":"2025-05-23T10:58:40+07:00","caller":"backoff/backoff.go:106","func":"github.com/wakatime/wakatime-cli/pkg/backoff.shouldBackoff","message":"exponential backoff tried 6 times since 2025-05-23T10:57:46+07:00, will retry again after 2025-05-23T11:14:40+07:00","version":"v1.115.3","os/arch":"linux/amd64","file":"/home/hans/.wakatime/wakatime.log","time":1747972714.2192502,"plugin":"vscode/1.100.2 vscode-wakatime/25.0.3","lineno":17890} {"level":"debug","now":"2025-05-23T10:58:40+07:00","caller":"offline/offline.go:73","func":"github.com/wakatime/wakatime-cli/cmd/heartbeat.SendHeartbeats.WithQueue.func2.1","message":"pushing 1 heartbeat(s) to queue after error: won't send heartbeat due to backoff without proxy","version":"v1.115.3","os/arch":"linux/amd64","file":"/home/hans/.wakatime/wakatime.log","time":1747972714.2192502,"plugin":"vscode/1.100.2 vscode-wakatime/25.0.3","lineno":17890} {"level":"error","now":"2025-05-23T10:58:40+07:00","caller":"cmd/run.go:328","func":"github.com/wakatime/wakatime-cli/cmd.runCmd","message":"failed to run command: sending heartbeat(s) failed: won't send heartbeat due to backoff without proxy","version":"v1.115.3","os/arch":"linux/amd64","file":"/home/hans/.wakatime/wakatime.log","time":1747972714.2192502,"plugin":"vscode/1.100.2 vscode-wakatime/25.0.3","lineno":17890} {"level":"debug","now":"2025-05-23T10:58:40+07:00","caller":"cmd/run.go:346","func":"github.com/wakatime/wakatime-cli/cmd.runCmd","message":"command failed with exit code 112","version":"v1.115.3","os/arch":"linux/amd64","file":"/home/hans/.wakatime/wakatime.log","time":1747972714.2192502,"plugin":"vscode/1.100.2 vscode-wakatime/25.0.3","lineno":17890}

[alanhamlett]

https://wakatime.com/faq#finding-error-messages-in-logfiles

We need the real error message not the normal won't send heartbeat due to backoff one.

[hidesec]

@alanhamlett Do you mean this? I am using two editors.

{"caller":"pkg/api/api.go:103","file":"C:/Users/raiha_blgzntx/AppData/Roaming/JetBrains/IntelliJIdea2021.2/consoles/db/00ac29e0-7c67-4b2a-90e0-35440dc4aeec/console.sql","func":"api.isLocalIPv6","is_write":true,"level":"warning","message":"failed dialing to detect default local ip address: dial udp 143.244.210.202:80: connect: A socket operation was attempted to an unreachable host.","now":"2023-04-18T03:08:42+07:00","os/arch":"windows/amd64","plugin":"idea/2021.2.2 idea-wakatime/14.1.1","time":1681743772.74,"version":"v1.73.0"} {"caller":"cmd/run.go:301","file":"C:/Users/raiha_blgzntx/AppData/Roaming/JetBrains/IntelliJIdea2021.2/consoles/db/00ac29e0-7c67-4b2a-90e0-35440dc4aeec/console.sql","func":"cmd.runCmd","is_write":true,"level":"error","message":"failed to run command: sending heartbeat(s) failed: api error: failed making request to \"https://api.wakatime.com/api/v1/users/current/heartbeats.bulk\": retry request failed: Post \"https://2604:a880:4:1d0::2a7:b000/api/v1/users/current/heartbeats.bulk\": dial tcp [2604:a880:4:1d0::2a7:b000]:443: connectex: A socket operation was attempted to an unreachable network.. original error: Post \"https://api.wakatime.com/api/v1/users/current/heartbeats.bulk\": dial tcp: lookup api.wakatime.com: no such host","now":"2023-04-18T03:08:42+07:00","os/arch":"windows/amd64","plugin":"idea/2021.2.2 idea-wakatime/14.1.1","time":1681743772.74,"version":"v1.73.0"} {"caller":"cmd/run.go:301","file":"C:/Users/raiha_blgzntx/AppData/Roaming/JetBrains/IntelliJIdea2021.2/consoles/db/7da71c2a-06f8-4a52-9a4f-bfe0a4fc13dd/console.sql","func":"cmd.runCmd","is_write":true,"level":"error","message":"failed to run command: sending heartbeat(s) failed: api error: failed making request to \"https://api.wakatime.com/api/v1/users/current/heartbeats.bulk\": Post \"https://api.wakatime.com/api/v1/users/current/heartbeats.bulk\": dial tcp 143.244.210.202:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.","now":"2023-05-04T14:02:06+07:00","os/arch":"windows/amd64","plugin":"idea/2021.2.2 idea-wakatime/14.1.1","time":1683183685.522,"version":"v1.73.0"} {"caller":"cmd/run.go:301","file":"C:/Users/raiha_blgzntx/AppData/Roaming/JetBrains/IntelliJIdea2021.2/consoles/db/7da71c2a-06f8-4a52-9a4f-bfe0a4fc13dd/console.sql","func":"cmd.runCmd","is_write":true,"level":"error","message":"failed to run command: sending heartbeat(s) failed: rate limited: won't send heartbeat due to backoff","now":"2023-05-04T14:02:14+07:00","os/arch":"windows/amd64","plugin":"idea/2021.2.2 idea-wakatime/14.1.1","time":1683183723.028,"version":"v1.73.0"}

[alanhamlett]

Yes that's it. It says the DNS lookup failed. Try changing locations to a different internet provider and see if it works?

[hidesec]

@alanhamlett I have already changed my location and internet provider, but I still get the same error. I'm using two laptops and two different code editors. One laptop is using IntelliJ as the code editor, and the other one is using VSCode.

[hidesec]

@alanhamlett I have new Error on debug mode.

{"level":"debug","now":"2025-05-24T08:17:05+07:00","caller":"offline/offline.go:73","func":"github.com/wakatime/wakatime-cli/cmd/heartbeat.SendHeartbeats.WithQueue.func2.1","message":"pushing 1 heartbeat(s) to queue after error: invalid response status from \"https://api.wakatime.com/api/v1/users/current/heartbeats.bulk\". got: 429, want: 201/202. body: \"{\\\"error\\\": \\\"Consuming heartbeats has been disabled for account cabbd23d-fa4c-49f4-9dbe-3d602a215339.\\\"}\"","version":"v1.115.3","os/arch":"linux/amd64","file":"/home/hans/.wakatime/wakatime.log","time":1748049420.734245,"plugin":"vscode/1.100.2 vscode-wakatime/25.0.3","lineno":189}

[alanhamlett]

Consuming heartbeats has been disabled for account cabbd23d-fa4c-49f4-9dbe-3d602a215339.

That usually happens when some automation is detected on the account. Were you tailing a log file in your IDE that constantly updated, or something similar?

[hidesec]

Several times I checked the logs in my IDE.

[alanhamlett]

Checking is fine and normally even leaving the logfile open in vscode doesn't trigger activity, but we've seen some instances where people keep one vscode window always open with the logfile active and a plugin to tail/scroll to the end of the file when it updates. Instead, we recommend using the vscode Terminal or Output window to tail log files because the Editor window is meant only for editing files not viewing, and editing a logfile that's constantly updating tricks the vscode-wakatime plugin into sending code stats as if you were editing that logfile the whole day. A few days of that and your account gets disabled for automation.

[alanhamlett]

@hidesec Looking at your public profile, I see days with 22+ hours with the default 15 mins Keystroke Timeout used on all public profiles. That does seem like more coding than normally possible... is any of that from tailing log files in vscode or other automated activity?

If we can look at your workflow, maybe we can fix the vscode extension to not track this automated activity. Another solution is excluding any log files by path in your ~/.wakatime.cfg file, but that only solves it for you not for everyone else having this issue.

[BillyGalbreath]

Can you fix mine @alanhamlett? I've had a really good past few weeks of coding after a long period of lack of motivation. I don't work, am disabled, and I barely sleep. so I have all the time in the world to code.

[alanhamlett]

Can you fix mine @alanhamlett? I've had a really good past few weeks of coding after a long period of lack of motivation. I don't work, am disabled, and I barely sleep. so I have all the time in the world to code.

I already manually lifted the leaderboard ban from your account earlier, but the leaderboard only updates a few times per day.

Also there's https://crackboard.dev which updates hourly and is powered by WakaTime.

[alanhamlett]

@hidesec, i've also removed the ban from your account so your code stats should sync up for the past few days. It only syncs when you're coding, since the plugin only runs when there's activity in your IDE. However, for your account since it was fully disabled we should look into what triggered that. On our end it was triggered from too many hours per day in the same file, but we have many similar checks so it could be another reason in the future unless we figure out the root cause.

[Swag-blips]

Hello @alanhamlett — I came here from Reddit after seeing a similar issue. It looks like a ban was placed on my account as well, but I don't have any tail logfiles or even close to 20 hours on a single file.

Could you please review my account? I'm happy to provide more context if needed. Thanks in advance!

[alanhamlett]

Hello @alanhamlett — I came here from Reddit after seeing a similar issue. It looks like a ban was placed on my account as well, but I don't have any tail logfiles or even close to 20 hours on a single file.

Could you please review my account? I'm happy to provide more context if needed. Thanks in advance!

Sure, I just removed the ban for your account too. Yours was triggered by 12+ hours without breaks for multiple days (continuous coding for 12 hrs), which was flagged as automation.